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.
Currently there is no convenient way to add a custom module to a NB platform application which uses WebServices with JAX-WS. It would be nice to add a module to the platform cluster (maybe disabled by default) that can provide JAX-WS access to other modules. There is a JAX-WS module in Java1 cluster but it's limited only to some friends. The only way is to package up a custom library wrapper module for JAX-WS.
Existing module could be given general, rather than friend, access; I'm not sure why it has friend-only access since it is obviously based on APIs which are supposed to be stable. Unlikely to put anything of the sort in the platform cluster. Issue #96711 would anyway make it unnecessary (assuming you are targeting a JRE version which includes the desired packages), since access to JRE packages would be permitted by default.
Obsolete milestone, please reevaluate
This issue seems to be gone, however using Java 6 + JAX-WS 2.1 API + NetBeans Platform is still not possible.
Adding JAX-WS 2.1 and JAXB 2.1 Libraries are still not possible to an NB Platform application as it requires friendship.
I've just checked the sources and it seems that "JAX-WS 2.1 and JAXB 2.1 Libraries" is OK as it provides the API Libraries to standard java projects. The thing is really needed is JAX WS 2.1 API module, which contains JAX-WS 2.1 and JAXB 2.1 API without the runtime. Unfortunately or Fortunately the NetBeans classloader rules doesn't allow to load the runtime classes even they are present in java 6 (for JAX WS 2.0). So We still have to provide an other module with runtime jars in order to make NetBeans platform usable as a Rich Client Platform!
Possibly WONTFIX since #96711 is implemented for 6.1.
Really solved. Closing.