Win a copy of Cross-Platform Desktop Applications: Using Node, Electron, and NW.js this week in the JavaScript forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

Generating client-side artifacts from the client machine  RSS feed

 
Prasanna Wamanacharya
Ranch Hand
Posts: 143
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello,

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.

TIA
 
Ivan Krizsan
Ranch Hand
Posts: 2198
1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi!
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.
Best wishes!
 
Prasanna Wamanacharya
Ranch Hand
Posts: 143
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks for replying Ivan!


Try pasting the XML schema URL in a browser on a remote machine to see if you can access the schema.


I did try it, and the schema was inaccessible on this URL - http://10.11.3.138:9080/EDR/EventDataReceiverService_schema1.xsd.

However, it was accessible on this URL - http://10.11.3.138:9080/EDR/EventDataReceiverService/EventDataReceiverService_schema1.xsd. I tried passing this location to wsimport using the -b option, but it still tries to access the schema at the first location.

Not sure what is going wrong here.
 
Ivan Krizsan
Ranch Hand
Posts: 2198
1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi!
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.
Best wishes!
 
Prasanna Wamanacharya
Ranch Hand
Posts: 143
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Looks like Websphere is exhibiting a similar behaviour. How do we get around it in Glassfish? Maybe a similar fix might work in Websphere.
 
Ivan Krizsan
Ranch Hand
Posts: 2198
1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi!
I have never tried to "get around it" in GlassFish, since it never caused me any problems.
Best wishes!
 
It is sorta covered in the JavaRanch Style Guide.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!