Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I think you should use inheritance instead of generics. Given an XML like this:</p> <pre><code>&lt;?xml version="1.0" encoding="UTF-8"?&gt; &lt;response xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"&gt; &lt;id&gt;000000&lt;/id&gt; &lt;results&gt; &lt;result xsi:type="X1Result"&gt; &lt;year&gt;2003&lt;/year&gt; &lt;title&gt;Lorem Ipsum&lt;/title&gt; &lt;items&gt; &lt;item&gt;I1&lt;/item&gt; &lt;item&gt;I2&lt;/item&gt; &lt;/items&gt; &lt;/result&gt; &lt;result xsi:type="X1Result"&gt; &lt;year&gt;2007&lt;/year&gt; &lt;title&gt;Dolor sit amet&lt;/title&gt; &lt;items&gt; &lt;item&gt;K1&lt;/item&gt; &lt;item&gt;K2&lt;/item&gt; &lt;/items&gt; &lt;/result&gt; &lt;/results&gt; &lt;/response&gt; </code></pre> <p>You can dynamically bind your <code>&lt;result&gt;</code> entries. You have a top-level type:</p> <pre><code>@XmlAccessorType(XmlAccessType.FIELD) @XmlType(name = "XResult") @XmlSeeAlso({ X1Result.class })public abstract class XResult { } </code></pre> <p>And you have implementing classes:</p> <pre><code>@XmlAccessorType(XmlAccessType.FIELD) @XmlType(name = "X1Result") public class X1Result extends XResult { @XmlElement(name = "year") private String year; @XmlElement(name = "title") private String title; @XmlElementWrapper(name = "items") @XmlElement(name = "item") private List&lt;String&gt; items; ... } </code></pre> <p>Use the top-level type in your XResponse class:</p> <pre><code>@XmlRootElement(name = "response") @XmlAccessorType(XmlAccessType.FIELD) public class XResponse { @XmlElement(name = "id") private String id; @XmlElementWrapper(name = "results") @XmlElement(name = "result") private List&lt;XResult&gt; results; ... } </code></pre> <p>And you can unmarshall using the top-level type:</p> <pre><code>context = JAXBContext.newInstance(XResponse.class, XResult.class); Unmarshaller unmarshaller = context.createUnmarshaller(); XResponse response = (XResponse) unmarshaller.unmarshal(new File("testfile.xml")); List&lt;XResult&gt; results = response.getResults(); for (XResult object : results) { System.out.println(object.getClass()); } </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POJAXB unmarshalling with java generics
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USdavidfmatheson
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThe code above initializes `XResult` instead of `X1Result` and therefore it gives error since it is an abstract class. Besides the content of the xml is coming from a legacy system and there is no `xsi:type` information available. (although I may add it programmatically)
      singulars
      1. PO
      1. USAlper
    2. COThe code will instantiate an `X1Result` if the `xsi:type` is there. At least, that's what it does for me. Good luck.
      singulars
      1. PO
      1. USdavidfmatheson
 

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