Gentlemen,
We are developing a series of xml messages that have a degree of commonality
in their elements. For example, there is a common header element that
contains credentials etc. These common elements have been factored into
separate schemas and then "included" in the messages.
When we use the source generator, it creates classes for these include
statements in each package that contains the included elements. The
messages are processed by a single ejb - and then these common classes must
be fully qualified to avoid the "ambiguous" error messages.
Do you know of a way to avoid this? What we had thought of was an option in
the SourceGenerator to not generate classes for "included" elements.
Art Blomberg
SynXis Hospitality Development
303 595-2515
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
