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.
There is a group of users who develop plain jax-ws services, and are grouped around jax-ws.dev.java.net or xwss.dev.java.net. To support these users, it would be good if we provide support for plain-jaxws (no jsr109) development as well, e.g. by adding checkbox to EE5 WS wizards: 'Plain JAX-WS', or something like that, with 109 staying still as the default. More importantly, this approach would help also in migration from Tomcat to GF: when users develop services on Tomcat, they should be able to seamlessly move to GF and continue in their development there. Also, this approach helps those community members which want to use bleeding edge jars for their development, as those usually do not work well or at all with jsr109.
This is being deferred and not included in NB 6.0
It seems there are customers who would like to use older servers with JAX-WS. For those, AS9 and JSR109 is not a choice. I think this feature gets more important.
moving opened issues where TM != dev to TM=TBD