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.
NB5.5 RC1 create new WP projct (j2ee1.4) - add wsdl file via url: http://api.google.com/GoogleSearch.wsdl - add ok - click on the GoogleSearchService node to see its property Web Serivices Port : 0 (no meaning for always 0) Web Serivices URL : file:/C:/XXXXX/Temp/GoogleSearch.wsdl (its should be same url address as user added) PortName should be GoogleSearchPort or something like that and url should be: http://api.google.com/GoogleSearch.wsdl
Yes, the information is really confusing. Do you really think this is a P2 bug ?
Please, use priority according to guidelines: http://qa.netbeans.org/bugzilla/bug_priority_guidelines.html It seems as P3 bug for me.
> Web Serivices Port : 0 (no meaning for always 0) Sure, this is valid bug, but something like P3 if not P4 - you can see how many and which ports are there if you expand the node. > Web Serivices URL : file:/C:/XXXXX/Temp/GoogleSearch.wsdl (its should be same url address as user added) Web Services URL property points the user to the URL which has been actually used for building the client. There's also Web Service Address property which shows where the service is deployed. So I don't see this part as a bug.
Changing priority to P3.
Related to JAX-RPC nodes
Obsolete milestone, please reevaluate
seems a trivial fix. targeting beta2.
Ajit?
In case we have same wsdl(url/file) used to create clients(in same or even different project), the webserviceregistry was not creating separate entries due to same servicename. I have added a check which distinguishes webserviceregistry entries based on not only service name but also local wsdl file url (which maps to the this client). fixed changeset 62ee4cb15873. see also 86974,127575.