Spec must be clear about the fact that JAX-RS on Java EE enforces underlying Servlets 3.0 and Autoconfiguration

[glassfishrobot]

The JAX-RS 2.0 spec should clearly say that when deploying to a Java EE container independent of the actual technology it is using no configuration is required by the application programmer or developer, but an auto-scanning mechanism MUST be applied by the Java EE container (even if that one is NOT based on Servlet 3.0). That is the only way to guarantee WORA in Java EE, since Java EE enforces Servlets, but does not enforce JAX-RS to base on Servlets. The spec currently only says how to deploy on Servlets but does not mandate Servlets itself. This unfortunately leaves room for implementations that are provided by Java EE containers, but that will not base on Servlets.

Environment

Jersey 2.0 M08-1, JAX-RS 2.0 M12, JRE 1.7.0_07

Affected Versions

[2.1]

[glassfishrobot]

• Issue Imported From: https://github.com/jax-rs/api/issues/295
• Original Issue Raised By:@glassfishrobot
• Original Issue Assigned To: @glassfishrobot

[glassfishrobot]

@glassfishrobot Commented Reported by mkarg

[glassfishrobot]

@glassfishrobot Commented @mpotociar said: Deferring for future re-evaluation. Currently only official supported EE deployment model is on top of a Servlet container.

[glassfishrobot]

@glassfishrobot Commented mkarg said: Maybe you misunderstood my intention. All I want to reach is that JAX-RS 2.0 clearly says that a Java EE container MUST support JAX-RS on top of Servlet 3.x, and any other possible support of JAX-RS is only additional.

[glassfishrobot]

@glassfishrobot Commented This issue was imported from java.net JIRA JAX_RS_SPEC-290