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: | Add jersey libraries into the server classpath for WL with JEE6 | ||
---|---|---|---|
Product: | serverplugins | Reporter: | Denis Anisimov <ads> |
Component: | WebLogic | Assignee: | Petr Hejl <phejl> |
Status: | VERIFIED FIXED | ||
Severity: | normal | CC: | arungupta, mmirilovic, pjiricka |
Priority: | P3 | ||
Version: | 7.2 | ||
Hardware: | PC | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | |
Bug Depends on: | |||
Bug Blocks: | 206527 |
Description
Denis Anisimov
2011-12-19 11:14:11 UTC
com.sun.jersey.* fixed in web-main e3ce5e8a2416 *** Bug 206796 has been marked as a duplicate of this bug. *** Filed https://bug.oraclecorp.com/pls/bug/webbug_print.showbug?c_rptno=13557884 for api.jar. (In reply to comment #0) > As an option : we can skip Jersey implementation specific jars at all. User > will be able to add them manually in its classpath. As I'm not an ws expert I don't want to make that decision. With the change in comment 3 all jersey libraries are added to CP. Denis, please evaluate whether only api jars should be added (which one?) or all jars you mentioned should be added (including jackson). I think you know better what users prefer and what is "right". Thanks. Integrated into 'main-golden' Changeset: http://hg.netbeans.org/main-golden/rev/e3ce5e8a2416 User: Petr Hejl <phejl@netbeans.org> Log: #206526 Add jersey libraries into the server classpath for WL with JEE6 (In reply to comment #4) > (In reply to comment #0) > > As an option : we can skip Jersey implementation specific jars at all. User > > will be able to add them manually in its classpath. > As I'm not an ws expert I don't want to make that decision. With the change in > comment 3 all jersey libraries are added to CP. > > Denis, please evaluate whether only api jars should be added (which one?) or > all jars you mentioned should be added (including jackson). I think you know > better what users prefer and what is "right". > > Thanks. com.sun.jersey.core_1.0.0.0_1-9.jar contains JAX-RS API . That API is a part of JEE6 spec and should be in the server classpath. All other classes are implementation classes and are not required ( from JEE6 spec ). The same situation is for GF3.1 actually : there is no separate API jar file but jersey-core.jar contains JAX-RS API along with some impl Jersey classes. But its Project UI node doesn't contain Jersey impl classes ( just JAR-RS API ). I don't know how it is done exactly. So the JAX-RS API classes are mandatory. On the other hand current approach is good enough : user could use some Jersey specific impl classes in his application. Such application could be non-portable because other JEE6 server could use different JAX-RS impl. So the decision about Jersey classes in the server classpath is not actually JAX-RS specific but mostly JEE server node design decision . I would prefer to keep current approach with Jersey classes in the server classpath. There was a request about some specific Jersey version some time ago ( but I'm not sure about exact usage case ) so probably it could be useful. Thanks, looks like we can consider this issue fixed. If we need any additional changes related to the Jersey-specific non-portable jars on classpath, let's file a separate issue for that. Integrated into 'releases', will be available in build *201202082200* or newer. Wait for official and publicly available build. Changeset: http://hg.netbeans.org/releases/rev/39f6b82b02cd User: Petr Hejl <phejl@netbeans.org> Log: #206526 Add jersey libraries into the server classpath for WL with JEE6 (transplanted from e3ce5e8a2416c7ee9d747207e7e1c0a14de4c48f) Verified in patched 7.1 build. com.sun.jersey.* jars available on classpath. |