|
Hi, The way Castor handles elements and
complex types can be changed. Basically this is due to authoring style
of schemas. Try changing the following setting and see
if this suite you better. http://www.castor.org/sourcegen.html#The-'type'-method Andy. From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Hi,
perhaps I
am missing something, haven't read the manual enough, am overlooking something,
but I have a question about the source generation and the use of complex types
in relation to the code generated. In short, why doesn't castor use the complex
type for input and output parameters, but instead does it use generated classes
named after the element name. Considering
the following example: <xs:complexType
name="Person"> <xs:complexType
name="HappyFamily"> Why does
castor generate a class for each element of the HappyFamily complex type? In other
words, why does castor generate the classes Mom, Dad, Child (extending Person).
In java:
HappyFamily
family = new HappyFamily(); Why can't
this be: HappyFamily
family = new HappyFamily(); Thanks,
Rutger
Lubbers
|
Title: XSD complexTypes and source generation.
- [castor-user] XSD complexTypes and source generation. rutger . lubbers
- RE: [castor-user] XSD complexTypes and source genera... Andrew Fawcett

