Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I tried combining the two schemas (that use the same element name) as you suggested earlier. </p> <p><em><strong>(note: I had to use the "Answer your own question" posting in order to include the examples, since the comment allows only limited space)</em></strong></p> <p>One problem I am having is that some of the sub-elements in the actual schema (I cant post the actual schema) use the same names (I had to recreate, below, to illustrate this case... -notice that schema1 and schema2 "group"s contain elements having the same name)... </p> <p>Here is the schemacombo.xsd: </p> <pre><code>&lt;?xml version="1.0" encoding="UTF-8"?&gt; &lt;xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified"&gt; &lt;xs:group name="schema1"&gt; &lt;xs:sequence&gt; &lt;xs:element name="AA"&gt; &lt;xs:complexType&gt; &lt;xs:sequence&gt; &lt;xs:element name="CC1" type="xs:string"/&gt; &lt;xs:element name="CC2" type="xs:string"/&gt; &lt;/xs:sequence&gt; &lt;/xs:complexType&gt; &lt;/xs:element&gt; &lt;xs:element name="BB"&gt; &lt;xs:complexType&gt; &lt;xs:sequence&gt; &lt;xs:element name="DD1" type="xs:string"/&gt; &lt;/xs:sequence&gt; &lt;/xs:complexType&gt; &lt;/xs:element&gt; &lt;/xs:sequence&gt; &lt;/xs:group&gt; &lt;xs:group name="schema2"&gt; &lt;xs:sequence&gt; &lt;xs:element name="AA"&gt; &lt;xs:complexType&gt; &lt;xs:sequence&gt; &lt;xs:element name="CC1" type="xs:string"/&gt; &lt;xs:element name="CC2" type="xs:string"/&gt; &lt;/xs:sequence&gt; &lt;/xs:complexType&gt; &lt;/xs:element&gt; &lt;xs:element name="BB"&gt; &lt;xs:complexType&gt; &lt;xs:sequence&gt; &lt;xs:element name="DD1"&gt; &lt;xs:complexType&gt; &lt;xs:sequence&gt; &lt;xs:element name="EE1" type="xs:string"/&gt; &lt;xs:element name="EE2" type="xs:string"/&gt; &lt;/xs:sequence&gt; &lt;/xs:complexType&gt; &lt;/xs:element&gt; &lt;/xs:sequence&gt; &lt;/xs:complexType&gt; &lt;/xs:element&gt; &lt;/xs:sequence&gt; &lt;/xs:group&gt; &lt;xs:element name="A"&gt; &lt;xs:complexType&gt; &lt;xs:choice&gt; &lt;xs:group ref="schema1" /&gt; &lt;xs:group ref="schema2" /&gt; &lt;/xs:choice&gt; &lt;/xs:complexType&gt; &lt;/xs:element&gt; &lt;/xs:schema&gt; </code></pre> <p>I've tried running </p> <pre><code>xjc schemacombo.xsd -b binding.xjb </code></pre> <p>...where binding.xjb contains </p> <pre><code>&lt;?xml version="1.0" encoding="UTF-8"?&gt; &lt;jxb:bindings xmlns:jxb="http://java.sun.com/xml/ns/jaxb" xmlns:xs="http://www.w3.org/2001/XMLSchema" jaxb:version="2.0"&gt; &lt;jxb:bindings schemaLocation = "schemacombo.xsd" node="/xs:schema"&gt;&gt; &lt;jxb:schemaBindings&gt; &lt;jxb:bindings node="xs:group[@name='schema2']"&gt; &lt;jxb:nameXmlTransform&gt; &lt;jxb:modelGroupName suffix="2"/&gt; &lt;/jxb:nameXmlTransform&gt; &lt;/jxb:bindings&gt; &lt;/jxb:schemaBindings&gt; &lt;/jxb:bindings&gt; &lt;/jxb:bindings&gt; </code></pre> <p>...-A weak attempt, I know, and it does not work...i.e., running this yields:</p> <pre><code>parsing a schema... [ERROR] cos-element-consistent: Error for type '#AnonType_A'. Multiple elements with name 'AA', with different types, appear in the model group. line 49 of file:/C:/AAAAA_delegate/schemacombo.xsd [ERROR] cos-nonambig: AA and AA (or elements from their substitution group) violate "Unique Particle Attribution". During validation against this schema, ambiguity would be created for those two particles. line 49 of file:/C:/AAAAA_delegate/schemacombo.xsd Failed to parse a schema. </code></pre> <p>Do you have any suggestion for bindings statements or annotations that would fix this. --Note, I have still not seen customized binds work, yet. </p>
    singulars
    1. This table or related slice is empty.
    1. POHow to use JAXB to process messages from two separate schemas (with same rootelement name)
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USsairn
    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. VTModeratorReview
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTModeratorReview
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI did not see your "answer your own question" when I commented on my other answer. you have the same issue here that you originally did when I suggested using the choice/group reference. you have definitions for the same element with differing types. you cannot do that and expect the schema to be valid. (this isn't perl code after all ;-) ) I don't think you'll be able to nicely modify your schema in a way to get around all these duplicate element definitions. in this example you could move the AA into a sequence definition in the "A" element complex type. (continued in next comment)
      singulars
      1. PO
      1. USHelter Scelter
    2. CObut the definition of the DD1 element as both a simple type (string) and a complex type is really what prevents you from overcoming your issue in this case. I can't think of a way around this other than to follow my other suggestion from the other answer, which is to generate your JAXB stubs separately for each schema, and attempt to parse your message using both JAXB contexts with validation enabled.. it's not clean by any means, but it might allow you to deal with this situation better than trying to munge the schemas into some semblance of unity. square peg, round hole know what I mean?
      singulars
      1. PO
      1. USHelter Scelter
    3. COUndertand. And, thanks for your efforts, Helter!.. --At the very least you've helped me to stop wasting my time on a dead end path.
      singulars
      1. PO
      1. USsairn
 

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