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.
The artifacts are created in the org.netbeans.j2ee.wsdl.creditreport which is the target namespace for the wsdl file. If I want to customize the package, I can use the following wsimport command
Running this command outputs all the java artifacts in the com.test package. However, my ultimate goal is to use a jaxb binding file to customize the wsimport output. Therefore, I created a binding file to do the package customization. That file contains the following
Then, I run the following command
For some reason, this only partially works. Some of the artifacts are generated in com.test package and more are generated in the org.netbeans.j2ee.wsdl.creditreport. Can someone explain what is wrong with my jaxb bindings file? Why does the customization not apply to all the generated artifacts?
I found this link while searching for an answer to my errors. I am a full-fledged greenhorn to Java WS's, not to mention this being my very first post, so it may not even be relevant to your needs but I thought I would try.
Thanks for your reply. I managed to resolve the issue using a combination of both JAX-WS and JAXB binding files when using wsimport. The implementation above only used jaxb customizations which generated schema types artifacts. However, the generated artifacts for the service endpoint interface and the port accessor methods where being generated in a package structure relating to their target namespace in the wsdl. To override/customize this behavior, a JAX-WS binding file is required. This bindings file is basic, specifying the wsdl location and the package where the generated artifacts should be placed.
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com