Local WSDL-Path from dev-system after deployment on productive system

[hendrik]

Hi everybody!

I created a little system that consumes multiple webservices using NB 6.5.1. If I run the app locally on a Tomcat 6, everything works beautifully.

After I deploy this app to a Tomcat 6.0.18 on a linux-server, I get the following error:

javax.xml.ws.WebServiceException: Failed to access the WSDL at: file:/C:/Documents%20and%20Settings/<username>/My%20Files/NetBeansProjects/Appname/src/conf/xml-resources/web-service-references/ShoppingService/wsdl/developer.ebay.com/webservices/latest/ShoppingService.wsdl. It failed with:
/C:/Documents%20and%20Settings/<username>/My%20Files/NetBeansProjects/Appname/src/conf/xml-resources/web-service-references/ShoppingService/wsdl/developer.ebay.com/webservices/latest/ShoppingService.wsdl (No such file or directory).

So basically it tries to read the WSDL not from the real location on the web, but from the location it got downloaded to on my Windows development machine. If I copy the wsdl to the above path on linux, everything works fine.

Is there a way to tell wsimport to always use the remote URL? Or can I configure it to use a relative path inside my webapp? How could I do this using NB?

Thank you so much in advance!
Kind regards,
Hendrik

[hendrik]

Maybe I should have searched 5min longer, found the following solution:
http://forums.netbeans.org/viewtopic.php?t=7615

[domaz]

I had the same problem- the catalog.xml fix just does not work so don't waste your time with that.
Easiest way to fix this is to make a directory on the server called c:\wsdl or whatever. Make a similar directory on your development box (and all your other developers boxes). Then open jaxws-build.xml find the <wsimport line, change wsdl= from the funky stuff NetBeans put's in there too:
wsdl="file:/C:/wsdl/YourService/YourService.wsdl". Seems to be the best work-around.

[Manuel Mall]

Not sure which thread you are responding to as you didn't include the
original message but I just wanted to say that the catalog.xml solution as a
flexible way to package and reference WSDL files works just fine for me.

On deployment all my WSDL files are put into META-INF/wsdl/... and the
catalog maps the path used at wsimport time to the META-INF/wsdl/...
location.

For example this entry in META-INF/jax-ws-catalog.xml:

<system systemId="file:/oscar/wsdl/sforce/enterprise.wsdl"
uri="wsdl/sforce/enterprise.wsdl"/>

maps my SalesForce WSDL which is taken by wsimport from my local filesystem
(a Unix system in this case) and maps it to
META-INF/wsdl/sforce/enterprise.wsdl.



Domazlicky, Eric wrote:

[cfsavant]

I am getting this same problem in 7.1