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.