Hi,

it is no suprise to me that things work partially only. Here's why.

The binding definition

<elementBinding name="/C">
  <java-class name="ZZZZ"/>
</elementBinding>

defines a a new Java class name for the Java class generated from the
global element definition

<xsd:element name="C">
...
</xsd:element>

So far, so fine. But for the second binding definition, there's no
corresponding global element definition with the name 'B'. In other
words, this will never work.

Having said that, what artifact should be affected by the second binding
at all ?

Regards
Werner

K wrote:
> Just checking to see if this is a bug. Using codegen with 1.2, I
cannot map an element in certain cases (all other cases I've tried work
fine). Any help would be appreciated.
> 
> ** given an xsd that defines B and C in A:
> 
>   <xsd:element name="A" type="A_Type"/> 
>   <xsd:complexType name="A_Type"> 
>     <xsd:sequence> 
>       <xsd:element name="B" type="B_Type"/> 
>       <xsd:element ref="C"/>
>     </xsd:sequence> 
>   </xsd:complexType> 
>  <xsd:complexType name="B_Type"> 
>     <xsd:sequence> 
>       <xsd:element name="D" type="xsd:string"/>
>     </xsd:sequence> 
>   </xsd:complexType> 
>  <xsd:element name="C">
>    <xsd:complexType>
>     <xsd:sequence>
>       <xsd:element name="E" type="xsd:string"/>
>     </xsd:sequence>
>   </xsd:complexType>
>  </xsd:element>
> 
> 
> 
> ** and a binding file of:
> 
>     <elementBinding name="/B">
>          <java-class name="YYYY"/>
>     </elementBinding>
> 
>     <elementBinding name="/C">
>          <java-class name="ZZZZ"/>
>     </elementBinding>
>  
> 
> ** B is not changed to YYYY but C is changed to ZZZZ
> 
> Thanks,
> Keith
> 
> 
> 
> 
>       

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply via email to