Hiya, Why actually is 'type' not the default for this property? For me it's the most natural way to generate the code.
I've read the docs about the castorbuilder.properties before and set several options for my project to generate the sources that I want. (J2 types, get references to actual collections, like that.) However, when I looked back now at the description of this option I wouldn't have guessed from the docs that this is the option that I needed... Regards, --Tim -----Original Message----- From: Andrew Fawcett [mailto:[EMAIL PROTECTED] Sent: woensdag 30 juli 2003 11:11 To: [EMAIL PROTECTED] Subject: Re: [castor-dev] SourceGenerator questions As regards point 2), use the following setting in castorbuilder.properties. org.exolab.castor.builder.javaclassmapping=type Cheers. -----Original Message----- From: Leeuw van der, Tim [mailto:[EMAIL PROTECTED] Sent: 30 July 2003 10:05 To: [EMAIL PROTECTED] I have a couple of questions regarding the source-generator, which doesn't generate the code I like but looks like it should be able to do so quite easily... In my XSD I have defined some simpleTypes, and some complexTypes. My source is, for sake of argument, generated into a package my.foo 1) The simpleType definitions are put into a packapge my.foo.types, which is great, but the complexType definitions are not - why not? 2) In my XSD I specify roughly the following: <xsd:complexType name="foo1"> ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe castor-dev
