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.
Product Version: NetBeans IDE Dev (Build 200904011705) Java: 1.6.0_12; Java HotSpot(TM) Client VM 11.2-b01 System: Linux version 2.6.27-11-generic running on i386; UTF-8; en_US (nb) Glassfish v3 I have created web application and added a service. Application is deployed and run, it is possible to insert into any browser URL of service`s wsdl (and there is something loaded,there is at least some source code in the generated page). When I tried New|Web Service Client, inserted URL of service`s wsdl and clicked 'finish', it shown warning window that file could not be loaded, because URL is wrong The same result was returned when specifying the service for new client via project (see the new web service client dialog). I maybe did not understand how it should work, if so, you may close this issue(and maybe give an advice about how it works:) ). Anyway according to first few steps in testspec pointed by this issue`s URL, this does not look as correct behaviour.
Created attachment 79285 [details] messages.log
Created attachment 79286 [details] screenshot
From the screen shot you've sent it looks like the WSDL file at "http://localhost:8080/WSWebApp/MyWS?wsdl" is not available. Can you please check this URL in a browser ? Secondly, check also the schema URL, that is referenced from that wsdl. If those are correct, there is a problem in WS Client wizard. If not, the web service was not deployed correctly. The reason should be found in GlassFish V3 console. Please, bring in also the exact version of GlassFish V3. Is that GlassFish V3 Prelude ? Can you also test the same with GlassFish V2 ?
The url is working , and the generated page has some non-empty source (some xml..), I can attach it, if it is helpful. Also http://localhost:8080/WSWebApp/MyWS works and main page of web application(http....WSWebApp/ works as well So the problem should not be in URL, or non-wxisting page, the link clearly exists. I am using glassfish-v3-prelude-b28c. I may try it with glasfish-v2, but from what you said, it seems to me, that problem is with the new service client wizard.
I created a new java web application project, set it to use glassfish v2.1 (i think it is prelude as well), added a service, deployed it and run. The service in this project was then succesfully added. The same I tried then with v3 glasfish, to see any difference and now it seems to work fine... As I said, I probably missed or misunderstood something, maybe some setting. So, I think this one may be closed, sorry for inconvenience.