Status: Open (View Workflow)
Affects Version/s: glassfish_1.0.0.CR4
Fix Version/s: None
Component/s: GlassFish Containers
Similar Issues:Show 10 results
ARQ-1341 Warp JAX-RS testing ARQ-1563 Add support for JAX-RS 2.0 Client APIs ARQ-593 glassfish-resources.xml (application scoped resources) not loaded with glassfish-remote ARQ-613 GlassFish - succesful deployment with warning considered failed ARQ-1688 Drop Selenium 1.0 support ARQ-1213 Add support for GlassFish 3.0 container ARQ-346 Create a GlassFish 3.1 Embedded Container ARQ-1011 Support Groups of Containers of different Type ARQ-1212 Add support for GlassFish 2.x containers ARQ-398 Help GlassFish understand relative URIs
The GlassFish Remote and Managed containers use Jersey 1.x to communicate with the Admin REST API.
- Jersey changed package from com.sun to org.glassfish between 1.x and 2.x
- Jersey core bundles the JAX-RS 1.0 apis
This case some issues when you want to test JAX-RS 2.0 features on the client side using GlassFish 4.
You can't exclude the Jersey libs exposed and replace them with Jersey 2.0 because the package names changed.. And you can't really get JAX-RS 2.0 on ClassPath because Jersey 1.0 bundles the 1.0 APIs..
We need to replace the communication with the Admin API with something that can't interfere with the Container / User classpath.