Hi Angelina,
You can try adding the following to the castorbuilder.properties:
org.exolab.castor.xml.JavaNaming.upperCaseAfterUnderscore=true
This allows compatilibility with JavaNaming between 0.9.3.9 and 0.9.4.2
(basically the _ issue), however, perhaps something else may be causing
the problem you are seeing since I checked and JavaNaming is behaving
the same in both versions of the class for field and class names when it
sees a an all UPPERCASE name.
Can you attach the Schema for APLSchema:BaseServerType and
APLSchema:ListServerType so I can run the test here.
Thanks,
--Keith
> [EMAIL PROTECTED] wrote:
>
> I recently upgraded from Castor 0.9.3.9 to 0.9.4.2. As part of this
> effort, we had to add a new namespace to our schemas just to get the
> generator to work. That is the ONLY change we made. But, once we did
> that Castor is now generating stuff like this:
>
> For the schema elements like:
>
> <ns:element name="SERVERS" minOccurs="0" maxOccurs="1">
> <ns:complexType>
> <ns:complexContent mixed="true">
> <ns:extension base="APLSchema:BaseServerType">
> <ns:sequence>
> <ns:element name="SERVER"
> type="APLSchema:ListServerType" minOccurs="0" maxOccurs="unbounded"/>
> </ns:sequence>
> </ns:extension>
> </ns:complexContent>
> </ns:complexType>
> </ns:element>
>
> I'm getting a class named "Servers" in "SERVERS.java", which obviously
> won't compile. I'm using "type" generation, and we basically only use
> Castor as a java class generator from our schema. There are MANY more
> examples of stuff like this (MoversDescriptor class in
> MOVERSDescriptor.java for example).
>
> With 0.9.3.9 the class names matched the file names properly.
>
> Any help would be greatly appreciated. I can also provide more schema
> files or examples if needed.
>
> Thanks!
>
> -Angelina Talley
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
