Databases
StackOverflow2013
Postsdbo
POJAXB Collections (List<T>) Use Pascal Case instead of Camel Case for Element Names
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POJAXB Collections (List<T>) Use Pascal Case instead of Camel Case for Element Names
    primarykey
    data
    text
    <p>I have a number of JAXB beans that are directly marshalled and unmarshalled using Jersey.</p> <p>E.g.</p> <pre><code>@XmlAccessorType(XmlAccessType.FIELD) @XmlType(name = "Artifact", propOrder = { "artifactId", "artifactType", "contentHash" }) @XmlSeeAlso({ EmailArtifact.class, ManagedDocArtifact.class }) @XmlRootElement(name ="Artifact") public class Artifact { protected String artifactId; protected String artifactType; protected String contentHash; ... ... ... } </code></pre> <p>If I create a GET method that returns a single artifact object. It correctly produces the XML:</p> <pre><code>&lt;Artifact&gt; &lt;artifactId&gt;293289392839283&lt;/artifactId&gt; &lt;artifactType&gt;EMAIL&lt;/artifactType&gt; &lt;contentHash&gt;2837873827322&lt;/contentHash&gt; &lt;/Artifact&gt; </code></pre> <p>Here I have been able to successfully control the name of the Artifact element to have a capital "A" at the beginning.</p> <p>However, I create a GET method that returns collection of artifact objects, I end up with:</p> <pre><code>&lt;artifacts&gt; &lt;Artifact&gt; &lt;artifactId&gt;293289392839283&lt;/artifactId&gt; &lt;artifactType&gt;EMAIL&lt;/artifactType&gt; &lt;contentHash&gt;2837873827322&lt;/contentHash&gt; &lt;/Artifact&gt; &lt;Artifact&gt; &lt;artifactId&gt;293289392839283&lt;/artifactId&gt; &lt;artifactType&gt;EMAIL&lt;/artifactType&gt; &lt;contentHash&gt;2837873827322&lt;/contentHash&gt; &lt;/Artifact&gt; &lt;/artifacts&gt; </code></pre> <p>As you can see the outer element for the collection has a lower case "A". In order to conform to our own internal standard I would like this to be a capital "A" - Artifacts.</p> <p>I can not see where this is possible to define within JAXB, is it actually the Jersey framework that is controlling this?</p> <p>Can we control of the element name generated for collections?</p> <p>Many thanks,</p> <p>James</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USjallch
    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. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POJAXB Collections (List<T>) Use Pascal Case instead of Camel Case for Element Names
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POJAXB Collections (List<T>) Use Pascal Case instead of Camel Case for Element Names
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POJAXB Collections (List<T>) Use Pascal Case instead of Camel Case for Element Names
      1. USChristian Schmizz
      1. VTFavorite
    1. CO1. AFAIK JAXB doesn't allow you to marshall a collection (e.g. `ArrayList<Artifact>`) as such. But it allows you to serialize an object which has a collection as a property. 2. I am not familiar with Jersey, but I guess you need to know whether is it JAXB which serializes each artifact separately and some other layer (Jersey) builds the whole document of the chunks or is it JAXB which procudes XML for the collection. 3. Could you post some code (or publish it somewhere) - how to call it? I was trying with simple JAXB but this doesn't mimic your set up.
      singulars
      1. POJAXB Collections (List<T>) Use Pascal Case instead of Camel Case for Element Names
      1. USGrzegorz Oledzki
    2. COI suspect that you are right - it is Jersey which is allowing me to marshall/unmarshall the collection of JAXB beans (I've raised this with the Jersey users group as well). Therefore I'm hoping that there is some configuration that allows me to set the name or the rules behind the XML element name for collections... We shall wait and see. As you point out, a workaround is to create a new JAXB bean - let's say "Artifacts" which has a single collection member e.g. List<Artifact> artifacts - this I feel though introduces a whole bunch of classes which don't add much value. Thanks for help. James
      singulars
      1. POJAXB Collections (List<T>) Use Pascal Case instead of Camel Case for Element Names
      1. USjallch
 

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