Win a copy of Svelte and Sapper in Action this week in the JavaScript forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Bear Bibeault
  • Junilu Lacar
  • Jeanne Boyarsky
  • Tim Cooke
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • salvin francis
  • Frits Walraven
  • Scott Selikoff
  • Piet Souris
  • Carey Brown

wsdl: how do i generate wsdl that places the type info in the main body instead of using xsd:import?

Posts: 24
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I've created a webservice, which I'm trying to access using an Actionscript 3.0 client.

Unfortunately the client cannot parse the wsdl since it trips up on the import here:

<xsd:import namespace=""; schemaLocation="http://localhost:9875/TestServer?xsd=1"/>;

However the AS3 client can access the Amzon SOAP service fine, which I've noticed does not do the import.

Thanks for any help
Ranch Hand
Posts: 2198
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Is it an option to generate the WSDL, then copy and paste the associated type information into the WSDL?
If so, then:
1. Place the modified WSDL in the WEB-INF/wsdl directory of your web service project.
2. Specify the WSDL of the web service in the @WebService annotation, using the wsdlLocation attribute.

Another alternative would be to deploy to GlassFish, which fixes WSDL and XSD locations on the fly, as the WSDL is requested.
Hope this helps!
Best wishes!
Posts: 3
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

You can generate a single WSDL instead of a wrapped one. For me the server was generating 2 wsdls due to difference in name space of SEI and implementation classes, if you carefully define namespaces, server will generate only one wsdl.

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

I'm facing a similar 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, but is not able to find the XSD.

Any help in fixing this would be much appreciated.

Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
    Bookmark Topic Watch Topic
  • New Topic