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.
JEE6 spec requires presence of JSR311. So J2EE server with JEE6 profile should have JSR311 API in its classpath. Such server should have also RESTful implementation specific classes that allow to run RESTful WS in its container. So RESTful configuration dialog should not extend project classpath with Jersey jar files. See also issue #204816.
Fix on GF side : web-main#fbfedfcd8985 I chose the way to fix JEE6 profile special case in any server plugin separately instead of common logic to avoid call to JaxRsStack within REST modules (in JEE6 case). Such approach allows to extend classpath with all Jersey libraries available : do not extend project classpath but some special classpath (like J2EE server) with jar files which will not be added into the resulting deployment unit.
Integrated into 'main-golden' Changeset: http://hg.netbeans.org/main-golden/rev/fbfedfcd8985 User: Denis Anisimov <ads@netbeans.org> Log: Fix for BZ#206527 on the GF side.
web-main#505e46a32c46 Fix for Weblogic
Integrated into 'main-golden' Changeset: http://hg.netbeans.org/main-golden/rev/505e46a32c46 User: Denis Anisimov <ads@netbeans.org> Log: Fix for BZ#206527 - Do not extend JEE6 project classpath with Jersey libraries ( Weblogic plugin ).