Post a Comment On: My Thoughts

Well processing the uddi v2 schema with JAXB is not straightforward.
JAXB tries to map each element, complextype, simpletype into a jaxb class. And v2 xsd contains some of these elements with the same names. As a result, it leads to an overlap in names of generated classes and hence you see the Error messages.

To overcome this problem, we need to customize the JAXB using Customization of JAXB Bindings.
See the Sample Code Nsure Uddi Project at Forge . Binding for JAXB Code Generations of uddiv2.xsd



The customization above handles the issue of duplicate class names. which results in the error reported.
Note: You need to include the above customization while generating the JAXB classes.