Daniel,
after a bit of source code readingh and test case writing, here's the complete
story. For most of the <simpletype> definitions (but enumerations), Castor will
not create Java classes perse. But when you start using those <simpleType>
definitions in your XMl schema (as part of element or attribute definitions),
Castor will use the information associatd with those simple type definions when
creating the field validators for the element/attribute in question.
Does this sort of address your concerns ?
Werner
________________________________
From: Daniel Nilsson [mailto:[EMAIL PROTECTED]
Sent: Freitag, 12. Jänner 2007 09:38
To: [email protected]
Subject: [castor-user] source code generation for OAGIS
Hi!
Is there anyone who uses the SourceCode generation, and the
marshalling/unmarshalling-framework with the OAGIS schemas? Does it work?
I have tried to generate some java-sources but I can't get it to
generate the sources for the imported namespace
http://www.openapplications.org/oagis/9/qualifieddatatypes/1.1
My original base-schema uses three imports (with namespaces) in it, and
two of them are generated, but the third (above namespace) is skipped.
I use a binding file in which I define the namespace-package relation
for all imported schemas, and I use the generateIMportedSchemas flag.
Castor doesn't say anything about any errors, it just doesn't generate
the classes.
Even if I try to only generate the sources for the Qualified schema I
can't get any data.
I attached this schema, together with imported schemas and the
binding-file (see qualified directory)
Does OAGIS use unsupported definitions?
Anybody have any ideas?
Regards
Daniel
