Hi Will, This is a known issue that will be fixed soon with the integration of the binding file: http://bugzilla.exolab.org/show_bug.cgi?id=882
It will allow you to specify a naming convention for the classes that you are generating from complexTypes, elements or groups. Sorry for the current inconvenience, Arnaud -----Original Message----- From: Will Etson [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 02, 2002 6:35 PM To: [EMAIL PROTECTED] Subject: [castor-dev] Possible FAQ addition or Bug Fix I'm using the recently released ebXML Customer information Schema (http://www.oasis-open.org/committees/ciq/) and attempting to using Castor's source code generator for XML. The source code generator would execute with out incident, however the classes would not compile due to a cyclic inheritance compiler error. Just by chance, a colleague of mine, engaged in .net development, tried it in with the .net schema compiler. It gave him errors that the ComplexTypes can not be named the same as elements. It turns out that castors�schema compiler suffers the same issue. After making the necessary changes to the schema, the Source code Generator works fine. The point: Should this be a FAQ item or a enhancement request? � I did read the docs, search the list,�the web, and bugzilla, so if this has been covered before please ignore. � P.S. I'm using castor 0.9.3.21 and I appreciate the great work. � Will Etson � ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe castor-dev
