RE: Exposing the WSDL file in a deployed web service

From: Ryan LeCompte <>
Date: Thu, 20 Oct 2005 10:16:54 -0400

Hi Ryan,


I solved this problem by putting all of the wsdl/xsd documents in the main
root folder for the deployable WAR file. Instead if putting the files in
/WEB-INF, I put them in "/" for the webapp. You'll also need to modify your
jaxrpc configuration file such that it points to that location.





From: Ryan Champlin []
Sent: Wednesday, October 19, 2005 11:00 PM
Subject: RE: Exposing the WSDL file in a deployed web service




Did you ever find a solution to this? We were planning on trying to do the
same but this same issue came to mind for me.






From: Ryan LeCompte []
Sent: Tuesday, September 13, 2005 8:56 AM
Subject: Exposing the WSDL file in a deployed web service


Hello all,


Normally you can access the WSDL file from a deployed web service (after
wsdeploy,etc.) by accessing it via http://localhost/Service?WSDL for
example. This seems to be working for me, however my WSDL document does a
schema import in order to import common data types defined in a .xsd
document. Although this .xsd file is included in the deployable WAR file for
the service, it doesn't seem to be accessible via the
http://localhost/Service?WSDL approach. Is there some extra step that I need
to do in order to make it available? If you point a tool such as wscompile
or .NET's "Wsdl.exe" utility to the http://localhost/Service?WSDL, it's not
able to download the entire WSDL since it can't seem to find the imported
schema file as well.


Any suggestions?