Databases
StackOverflow2013
Postsdbo
POXStream class cannot be resolved
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POXStream class cannot be resolved
    primarykey
    data
    text
    <p>I'm getting an XStream error with the following setup. I must be crazy. What's wrong?</p> <p>The request class</p> <pre><code>@XStreamAlias("RequestTO") public class RequestTO { @XStreamImplicit private List&lt;SkuMerchTO&gt; skuNumbers; ... } </code></pre> <p>The nested object class</p> <pre><code>@XStreamAlias("skuMerch") public class SkuMerchTO { @XStreamAlias("skuNumber") @XStreamAsAttribute private Integer skuNumber; @XStreamAlias("dept") @XStreamAsAttribute private Short department; @XStreamAlias("class") @XStreamAsAttribute private Short cls; @XStreamAlias("subClass") @XStreamAsAttribute private Short subClass; ... } </code></pre> <p>XStream code to decode the XML to an object:</p> <pre><code>XStream stream = new XStream(); stream.processAnnotations(SkuMerchTO.class); stream.processAnnotations(RequestTO.class); RequestTO request = (RequestTO)stream.fromXML(requestXml); </code></pre> <p>XML input string:</p> <pre><code>&lt;RequestTO&gt; &lt;skuMerch skuNumber="123456" dept="1" class="2" subClass="3"/&gt; &lt;skuMerch skuNumber="234567" dept="4" class="5" subClass="6"/&gt; &lt;/RequestTO&gt; </code></pre> <p>Error in Stacktrace:<br> ---- Debugging information ----<br> message : 2 : 2<br> cause-exception : com.thoughtworks.xstream.mapper.CannotResolveClassException<br> cause-message : 2 : 2<br> class : [...]RequestTO<br> required-type : [...]SkuMerchTO<br> path : /RequestTO/skuNumberList/skuMerch<br> line number : 3<br> .-------------------------------<br> com.thoughtworks.xstream.converters.ConversionException: 2 : 2 : 2 : 2<br> ---- Debugging information ----<br> message : 2 : 2<br> cause-exception : com.thoughtworks.xstream.mapper.CannotResolveClassException<br> cause-message : 2 : 2<br> class : [...]RequestTO<br> required-type :[..]SkuMerchTO<br> path : /RequestTO/skuNumberList/skuMerch<br> line number : 3<br> .------------------------------- </p> <p>If I create the objects and do toXML I get this:</p> <pre><code>&lt;RequestTO&gt; &lt;skuMerch skuNumber="0" dept="1" class="2" subClass="2"/&gt; &lt;skuMerch skuNumber="1" dept="1" class="2" subClass="2"/&gt; &lt;skuMerch skuNumber="2" dept="1" class="2" subClass="2"/&gt; &lt;/RequestTO&gt; </code></pre> <p>EDIT: The hilarious thing is, if do this: </p> <pre><code> stream.fromXML(stream.toXML(object)); </code></pre> <p>It still fails on the from XML part!</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USpclem12
    1. USpclem12
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POXStream class cannot be resolved
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POXStream class cannot be resolved
      1. USpclem12
      1. VTBountyStart
    3. VO
      singulars
      1. POXStream class cannot be resolved
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI don't understand the outputted XML if you have the annotation for aliasing `RequestTo` to `Request`...
      singulars
      1. POXStream class cannot be resolved
      1. USmre
    2. COmy bad, that was a typo. The alias is "RequestTO"
      singulars
      1. POXStream class cannot be resolved
      1. USpclem12
    3. COI entered your code (almost) directly, and had no issues from or to xml using xstream 1.4.2. Which version are you using? I did create a package for the classes, though.
      singulars
      1. POXStream class cannot be resolved
      1. UScmonkey
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload