I agree, but is there any way to prevent this from happening? Why would there be any real need to modify WSDL in first place?
Joined: Aug 19, 2005
lakhi singh wrote:Why would there be any real need to modify WSDL in first place?
It not really modified. The WSDL that you see is generated by the environment that hosts the endpoint based on the deployment information and endpoint characteristics.
Joined: Feb 12, 2009
It occurs when I try to generate java classes, not at published endpoints. Weblogic publishes modified WSDLs as such from deployed services.
WSDL that get bundled into jars look manipulated. I would like to figure out what deployment attributes can help clean up our WSDLs? I have lot of WSDL to deploy and prefer to get rid of extra noise with multiple namespace aliases. Any ideas?
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