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 201008310001) Operating System = Windows 7 version 6.1 running on x86 Java; VM; Vendor = 1.6.0_20 Runtime = Java HotSpot(TM) Client VM 16.3-b01 It might be related to issue #189997 I thought that having the interface class and the web service class named the same was the issue in the mentioned report. So I changed the endpoint to have a different name but the generated class didn't reflect the change.
Please, attach the interface (SEI) class and Web Service implementation class. Just a simple test case.
Created attachment 101811 [details] Sample project In this sample project I imported the WSDL file and changed the Service parameters. Notice that they are ignored when generating the service related files (refresh on service or compile)
Added required files without any more review of this issue.
There is just one class. It is Sample.java. This class has only one annotation WebService. The class is recognized as WS. So what's the problem ? "Annotations in WebService class are ignored" as result of WHAT ? If you still have the problem then please provide: - exact steps to reproduce - expected result - current result ( which is incorrect from your point of view ).
As explained renaming the endpoint in the annotation didn't change the generated code.
(In reply to comment #5) > As explained renaming the endpoint in the annotation didn't change the > generated code. This is not an explanation. Probably previous WS area owner ( Milan ) understood context and it was enough. I don't understand the problem at all. Where you did renamed endpoint and how ? Once again I need : - exact steps to reproduce - expected result - current result ( which is incorrect from your point of view ). Without this information the bug is incomplete and will have this status until you provide required information.
Ok, here we go: 1) Create a Web Service with the wizard 2) That will create a java class in the package you assigned with the following annotations: @WebService(serviceName = "<name>", portName = "<part name>", endpointInterface = "<end point>", targetNamespace = "http://service.server.core.xinco.bluecubs.com/", wsdlLocation = "WEB-INF/wsdl/XincoWebService/Xinco.wsdl") 3) Compile your project, it'll will generate a an ignored package (for versioning purposes) name Generated Sources (jax-ws) with the same package name selected in the wizard with all the classes there. There you'll find the <end point> class. 4) Modify the <end point> class name and recompile. 5) Notice the change is not propagated and the old end point class remains.
Still something is not clear. Do you mean com.bluecubs.xinco.server.service.Xinco class in the generated source folder in the sentence >Notice the change is not propagated and the old end point class remains. ? If this is correct assumption about your expectation then this is not a bug. Your service file is not an authority source of the WS. You have created the WS from wsdl file and a wsdl file is the authority source. Your WS impl class is GENERATED class based on the a WSDL file. The expected behavior ( which you assume ) cannot work automatically on compile even if the authority source is the WS impl class. This is the question either special refactoring action (and that should be RFE) or Refresh action. The refresh action should be called on the authority source of course. As I already said this is the WSDL file here. So only changes in the WSDL are reflected to the generated source.
Ok then. I was assuming wrong then.