Hi Mette,
you're right....it is the old known naming collision problem.
This problem will be solved in the next version of Castor with the source generator
binding
file that will give you more control on the generated classes.
Arnaud
-> -----Original Message-----
-> From: Hedin, Mette [mailto:[EMAIL PROTECTED]]
-> Sent: Wednesday, September 26, 2001 1:56 PM
-> To: [EMAIL PROTECTED]
-> Subject: [castor-dev] Documentation Question
->
->
-> In the latest version of the user guide, in section 2.3.2.14, I
-> see that a
-> complexType InvoiceType is mapped to a class InvoiceType and a
-> group Person
-> is mapped to a class Person. However, I believe it is quite
-> legal to declare
-> also a global complexType Person this would seem to result in a name
-> conflict between the two classes, and one would overwrite the other.
->
-> Is this a problem in the implementation or the documentation?
->
-> Mette Hedin
->
-> -----------------------------------------------------------
-> If you wish to unsubscribe from this mailing, send mail to
-> [EMAIL PROTECTED] with a subject of:
-> unsubscribe castor-dev
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
