wsimport problem: Found an answer

Last Updated on Sunday, 1 July 2012 Written by Chad Darby Friday, 15 July 2011

I was having problems using wsimport to generate SOAP clients from a wsdl. For a certain WSDL file, I kept getting the error:

[ERROR] A class/interface with the same name “xxxx” is already in use. Use a class customization to resolve this conflict.

I was stumped on this for a bit. StackOverflow saved the day! An answer was posted here that fits my exact problem.

The solution is to use “-B-XautoNameResolution” in your wsimport command. Worked like a charm 🙂  Sweet!

Did you like my blog post?

Signup now and receive an email when I publish new luv2code content.

I agree to have my personal information transfered to AWeber ( more information )

I will never give away, trade or sell your email address. You can unsubscribe at any time.

This entry was posted on Friday, 15 July 2011 and is filed under SOA. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

1 Comment

  1. Comments  links   |  Saturday, 05 September 2015 at 8:55 pm

    links

    wsimport problem: Found an answer | luv2code – For Software Developers Who Luv To Code: Java Architects and Developers – Java EE, J2EE, Blog – Chad Darby

Leave a Reply