This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Created attachment 148771 [details] Screen shot of error message Error message from NetBeans: Web Service Client can not be created by JaXWS:wsimport utility Reason A class/interface with the same name "com.psft.basic.BUSINESSUNITTypeShape" is already in use. Use a class customization to resolve this confilict Explaination: "A class/interface with the same name" is a known issue with JAXB. I did some research on the web and found some solutions to resolve this issue. Basically, you can either use a jaxb option "-B-XautoNameResolution" or customize class (or ObjectFactory method) binding (i.e. specify different names) for every jaxb types that have the same name. I used a combination of the two and it gets rid of all the errors of 'wsimport' and all the type classes are generated by 'wsimport'. However, NetBeans still report it as an issue. And I checked the specific class that it complains about in this case "BUSINESSUNITTypeShape" and I found that these classes are generated with the name "BUSINESSUNITTypeShapeXX" where 'XX' is a number appended to the name. I assume that is how the same name issue is resolved by jaxb option "-B-XautoNameResolution" of wsimport. But, NetBeans still report it as an error. I could not go further from here but have to report it as a bug with NetBeans. Note: If I customize class bindings for every jaxb types in the external binding file, it will likely resolve the problem. However, in my case, this is a huge amount of manual work since there are so many jaxb types that have the same name for this particular Web service I am trying to consume. The jaxb option "-B-XautoNameResolution" does seem to have resolved this issue on the 'wsimport' end. I'd like to know if there is something more I need to do in NetBeans or it is indeed a bug with NetBeans.
Milan, please evaluate ASAP. Thanks in advance.
Ran into this today.
Could you, please, provide exact steps to reproduce this problem? It would be ideal to attach a sample project exhibiting the described problem and emphasize the difference between the actual and the expected behavior. Thank you in advance.
Created attachment 154506 [details] The .wsdl that was used to generate using the Services Tab | Web Services | Add Web Service facilty that produced the error for me Note that this service is now firewalled and only accepts request from previously authorized IP addresses