This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 155132

Summary:	After some use, jax-ws webservices fail to access wsdl
Product:	xml	Reporter:	aperezymadrid <aperezymadrid>
Component:	WSDL Tools	Assignee:	Shivanand Kini <skini>
Status:	RESOLVED WONTFIX
Severity:	blocker
Priority:	P3
Version:	6.x
Hardware:	All
OS:	Windows ME/2000
Issue Type:	DEFECT	Exception Reporter:

Description aperezymadrid 2008-12-10 13:18:43 UTC

Hi

I've been using webservice clients in Java console applications and web applications, both with pax-prc and jax-ws for
more than a year. After rebuilding some applications, ws invocations begun to fail randomly. 

The error message is 
Failed to access the WSDL at:
<local path to project>/xml-resources/web-service-references/<path to network ws provider>.wsdl. **all path-separators
are "/"**
It failed with 
<local path to project>/xml-resources/web-service-references/<path to network ws provider>.wsdl **all path-separators
are now "\"**  (El dispositivo no está listo)  **means device not ready**  @ tryWithMex

In my opinion, the service creation artifact is looking for the ws provider in the local file system instead of the network.

Don't do tests on the development machine because the wsdl file exists there and it won't fail. Run the jar in another box.

After looking for a workaround I've found the workaround of andreou at
http://forums.java.net/jive/thread.jspa?messageID=224651&tstart=0 and it works fine. I'm keeping imported classes made
by the web service client tool, but overriding the webservice port generation.

Using jre 1.6.0_11

Comment 1 aperezymadrid 2008-12-10 13:22:43 UTC

pax-prc is a typo. it means jax-rpc

Comment 2 Martin Balin 2016-07-07 09:56:29 UTC

This old bug may not be relevant anymore. If you can still reproduce it in 8.2 development builds please reopen this issue.

Thanks for your cooperation,
NetBeans IDE 8.2 Release Boss