This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Is it an option to generate the WSDL, then copy and paste the associated type information into the WSDL?
If so, then:
1. Place the modified WSDL in the WEB-INF/wsdl directory of your web service project.
2. Specify the WSDL of the web service in the @WebService annotation, using the wsdlLocation attribute.
Another alternative would be to deploy to GlassFish, which fixes WSDL and XSD locations on the fly, as the WSDL is requested.
Hope this helps!
You can generate a single WSDL instead of a wrapped one. For me the server was generating 2 wsdls due to difference in name space of SEI and implementation classes, if you carefully define namespaces, server will generate only one wsdl.
I'm facing a similar problem on Websphere Application Server (WAS) 7. If I run wsimport on the machine which is running WAS, the client-side artifacts get generated properly. However, if I run wsimport on the client machine, it gives foll. error -
The wsimport command on the client machine is able to access the generated WSDL, but is not able to find the XSD.
Any help in fixing this would be much appreciated.