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.
|Summary:||Migrate websvc refactoring functionality to Retouche|
|Product:||webservices||Reporter:||Erno Mononen <emononen>|
|Component:||Code||Assignee:||Milan Kuchtiak <mkuchtiak>|
|Issue Type:||TASK||Exception Reporter:|
Description Erno Mononen 2007-04-12 15:58:19 UTC
The websvc refactoring support is disabled in 6.0 builds since it hasn't been migrated to the new Java infrastructure yet. The Refactoring API has also changed a bit in 6.0. Currently the functionality is in the j2ee/refactoring module, but it should be split into its own module, as is planned for the rest of the functionality in the module (JPA, EJB, Web). In 5.5 the websvc refactoring supports rename, safe delete, move and where used refactorings for webservices.xml, sun-jaxws.xml and jax-ws.xml. Furthermore, change parameters refactoring is supported for webservices.xml. The source code for these functionalities can be found in the o.n.m.j2ee.refactoring.[changeparam|moveclass|rename|safedelete|whereused] packages, the naming scheme for actual refactorings being rather obvious, e.g. JaxWs*Refactoring for jax-ws.xml refactorings and similarly for others. At the moment there are no plans to introduce a common support module for j2ee refactoring, so it is best to move whatever websvc related functionality you find useful to your new module.
Comment 1 Milan Kuchtiak 2007-06-18 10:34:28 UTC
For JAX-WS services, the WS configuration files (jax-ws.xml and sun-jaxws.xml) are listening to changes on WS Metadata Model (changes in annotations) so there is no refactoring necessary. Moreover, jax-ws.xml is not intended for user to change. For JAX-RPC web services, the Refactoring features are not working.
Comment 2 Milan Kuchtiak 2007-06-18 10:37:02 UTC
I changed the priority to P2 as the JAX-WS technology is preferred to JAX-RPC.
Comment 3 Srividhya Narayanan 2007-06-18 17:49:39 UTC
Removing plan60 as this has been agreed to be addressed after 6.0