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 6.0 (Build 200711231245) Java: 1.5.0_14; Java HotSpot(TM) Client VM 1.5.0_14-b03 System: Linux version 2.6.5-1.358 running on i386; UTF-8; en_US (nb) The errorbages don't do away when error is fixed by refreshing webservice client. Steps to reproduce: 1) create webproject A with some webservice (containing operation 'op') 2) create webproject B consuming webservice from A (using WSDL URL to locate the webservice) 3) create class in A calling the opearation 'op' 4) change name of operation op in project A and re-deploy project 5) change name of op in project B is the same way -> there are valid error badges 6) refresh WS client in B -> error badges don't go away util classes referencing WS are opened, building project does not help Seem that IDE should force reparsing related files somehow, when refreshing WS client.
moving opened issues from TM <= 6.1 to TM=Dev
Overtake.
reproducible with 6.7m3, got also autocomplition with old operation name, it was replaced with new one only after ide restart.
Reassigning all moonko's java/source bugs to myself.
Can someone from webservice (or QA) team please re-evaluate this whether it is still the case?
This is is still valid for 7.0dev. Error badge presents on the class node but not inside editor ( error annotation is removed after refreshing ). So there is really no refreshing of classes which uses webservice. One thing which I need to notice: the bug description is unbelievably inaccurate. It should be : 1) Create web service with some operation ( let's it call "op" ) in project A. 2) Deploy this web service to the app server. 3) Copy wsdl url of deployed web service. 4) Create project and Web service client based on wsdl file mentioned above. 5) Add some usage of web service client in the project B ( this is call to web service from project A ). 6) Change operation name in the project A and redeploy it. 7) Change operation name in the usage code in the project B. As result there will be error badge because operation with such name doesn't present in the generated WS reference ( project B). 8) Refresh WS reference in the project B. As result reference will be regenerated and changed operation now should remove error from the service usage. It happens only inside editor . Class node ( which contains usage of web service ) will be marked by error untill one close/open its editor. This is just cosmetic issue actually.
Works for me. I followed the described scenarios. Error badges in editor, and Project View disapear - after WS Reference Client Refresh (the checkbox "Also replace local wsdl file ..." in "Confirm Client Refresh" dialog must be checked). Tested with latest daily 7.4 build 20130820.