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.

Bug 196136 - Jersey not on runtime classpath in GlassFish 3.1 b43 (final)
Summary: Jersey not on runtime classpath in GlassFish 3.1 b43 (final)
Status: RESOLVED FIXED
Alias: None
Product: serverplugins
Classification: Unclassified
Component: GlassFish (show other bugs)
Version: 7.0
Hardware: PC Linux
: P2 normal (vote)
Assignee: Vince Kraemer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-28 22:57 UTC by David Konecny
Modified: 2011-03-03 16:41 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description David Konecny 2011-02-28 22:57:14 UTC 
While the Nb plugin has the jar in the GF classpath for compilation, it seems that the jersey client jar on the runtime is not used by default by the runtime, which in fact makes sense since the com.sun. ...jersey client API is not a Java EE 6 APIs, so this would make this Web App non portable to other app servers if our runtime would use it by default.

This issue asks for removal of Jersey jars from GF classpath for compilation.
Comment 1 Vince Kraemer 2011-03-01 00:10:16 UTC 
which jars need to be removed?  just jersey-client.jar or are there more?
Comment 2 David Konecny 2011-03-01 00:18:20 UTC 
Definitely that one but I'm not sure about others. Ludo might know more.
Comment 3 Vince Kraemer 2011-03-01 21:50:41 UTC 
it looks like i need to leave jersey-core.jar in the server classpath.  In GF 3.1, this has javax.ws.rs.* packages (which look like they are part of javaee... see http://download.oracle.com/javaee/6/api/overview-summary.html)
Comment 4 David Konecny 2011-03-01 22:06:23 UTC 
(In reply to comment #3)
> it looks like i need to leave jersey-core.jar in the server classpath.  In GF
> 3.1, this has javax.ws.rs.* packages (which look like they are part of
> javaee... see http://download.oracle.com/javaee/6/api/overview-summary.html)

The potential problem is that jersey-core.jar contains bunch of other com.sun.jersey.* packages. There should be a jar just with javax.ws.rs.* apis, no?
Comment 5 Vince Kraemer 2011-03-01 22:25:26 UTC 
(In reply to comment #4)
> (In reply to comment #3)
> > it looks like i need to leave jersey-core.jar in the server classpath.  In GF
> > 3.1, this has javax.ws.rs.* packages (which look like they are part of
> > javaee... see http://download.oracle.com/javaee/6/api/overview-summary.html)
> 
> The potential problem is that jersey-core.jar contains bunch of other
> com.sun.jersey.* packages. There should be a jar just with javax.ws.rs.* apis,
> no?

Should... yes.

Does... ?

I am checking on that...

3.0.1 has a modules/jsr311-api.jar that matches your description...  There isn't a matching jar in 3.1

jersey-core.jar is the closest parallel that I have found.
Comment 6 David Konecny 2011-03-02 17:30:11 UTC 
http://java.net/jira/browse/GLASSFISH-16119
Comment 7 Quality Engineering 2011-03-03 10:02:00 UTC 
Integrated into 'main-golden', will be available in build *201103030057* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
Changeset: http://hg.netbeans.org/main/rev/8be72d5321ea
User: vince kraemer <vkraemer@netbeans.org>
Log: #196136 : remove the non-Java EE 6 classes from the plugins J2eePlatformImpl