On Jan 14, 2013, at 10:16 AM, MK <[email protected]> wrote: > Daniel, > > how I can improve WS server side avoiding this situation? No I getting the > same problem with my WS. When I providing wsdls to others developers, they > generating wsdl2java get conflicts based on this thread problems.
The best option is to make sure ALL the objects in the package pretty much get included in the schemas for all the WSDL's, even if they aren't used in a particular WSDL. You can do that with @XmlSeeAlso annotations all over the place to make sure all the objects get included. You can also add a"jaxb.index" file into the package that is a simple list of simple class names in that package. That should be picked up by JAXB and then all those types included. -- Daniel Kulp [email protected] - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
