I'm facing a 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 on the WAS server, but is not able to find the XSD.
One of the possible solutions could be to generate the WSDL in such a manner that the schema definition is placed within the WSDL instead of it using <xsd:import>. If this is one of the solutions, how do I do it? If not, what is the proper solution?
Any help in fixing this would be much appreciated.
It looks like your WSDL is importing an XML schema that is not accessible remotely.
Try pasting the XML schema URL in a browser on a remote machine to see if you can access the schema.
I suggest that you investigate the behaviour of WebSphere.
GlassFish, for instance, will insert URLs in WSDLs and thus modify them "on the fly" - WebSphere maybe exhibit the same behaviour.