Support for JSR-330 annotations and CDI

[glassfishrobot]

As described in the JAX-RS 2.0 JSR (http://jcp.org/en/jsr/proposalDetails?id=339)::)

JAX-RS 1.1 was defined before JSR-330 was specified and as a result does not utilize 330 annotations, such as @Inject, as effectively as it could. This JSR will specify closer integration with 330 annotations that may potentially render some existing annotations in JAX-RS, such as @context, deprecated or redundant.

[glassfishrobot]

@glassfishrobot Commented
Reported by robc

[glassfishrobot]

@glassfishrobot Commented
Issue-Links:
is related to
JAX_RS_SPEC-35
JAX_RS_SPEC-67
JAX_RS_SPEC-72

[glassfishrobot]

@glassfishrobot Commented
@mpotociar said:
DI integration proposal drafted: http://java.net/projects/jax-rs-spec/pages/DI

[glassfishrobot]

@glassfishrobot Commented
@mpotociar said:
There are some interaction issues connected to this and we need to take more time to resolve them. Deferring to a future release.

[glassfishrobot]

@glassfishrobot Commented
reza_rahman said:
In a Java EE environment, it might also be very useful to be able to do this:

@Inject
Client client;

Or this:

@Inject @target("http://....")
WebTarget target;

Do let me know if anything needs to be explained further - I am happy to help.

Please note that these are purely my personal views and certainly not of Oracle's as a company.

[glassfishrobot]

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

[glassfishrobot]

@ggam Commented
Is this still on board for 2.1? Currently WildFly already treats JAX-RS resources as RequestScoped managed beans.

Having at least a basic integration like that would be very helpful.

[glassfishrobot]

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