Werner/Mattias,

We have encountered a problem with xsd:group.  Given this schema:

<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xmlns="http://www.fpml.org/2003/FpML-4-0";
targetNamespace="http://www.fpml.org/2003/FpML-4-0"; attributeFormD\
efault="unqualified" elementFormDefault="qualified">
     <xsd:group name="BuyerSeller.model">
                <xsd:sequence>
                        <xsd:element name="buyerPartyReference"
type="xsd:string" />
                        <xsd:element name="sellerPartyReference"
type="xsd:string" />
                </xsd:sequence>
        </xsd:group>

        <xsd:complexType name="ProductComplex" abstract="true">
                <xsd:sequence>
                        <xsd:element name="id" type="xsd:string" />
                </xsd:sequence>
        </xsd:complexType>

        <xsd:complexType name="EquityDerivativeBase">
                <xsd:complexContent>
                        <xsd:extension base="ProductComplex">
                                <xsd:sequence>
                                        <xsd:group
ref="BuyerSeller.model" />
                                </xsd:sequence>
                        </xsd:extension>
                </xsd:complexContent>
        </xsd:complexType>
</xsd:schema>

Castor generates a classes for

       EquityDerivativeBase.java
       ProductComplex.java

which we expected but it also generated

        BuyerSeller_model.java

which we did not.  In other words, it is as if Castor is expecting a
BuyerSeller_model element in the document, which it should not.  


_________________________________________
Goldman Sachs
Fixed Income, Currencies and Commodities 
Derivatives Core Architecture
85 Broad Street
New York, New York 10004

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

    http://xircles.codehaus.org/manage_email

Reply via email to