[GLASSFISH-18673] Use JSR 330 annotations in GlassFish Cloud Created: 01/May/12  Updated: 18/Feb/13  Resolved: 18/Feb/13

Status: Closed
Project: glassfish
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major
Reporter: tbeerbower Assignee: jwells
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

GlassFish modules should move away from using non standard Classes like Habitat and use standards based annotations and classes as specified by jsr 330(javax.inject.Inject, javax.inject.Provider etc.). To quote Jerome: "Classes like Habitat exposes too many APIs available to the users that makes the hk2 evolution very difficult. " Also some of the APIs are unclear (when to use habitat.getComponent() versus habitat.getByType() /habitat.getByContract() ).

So, the first step is to move away from Habitat (where ever possible) and use jsr 330 interface and annotations.

In order to do this, the hk2 team will be making the following changes to the GlassFish modules as described here ...

http://aseng-wiki.us.oracle.com/asengwiki/display/GlassFish/Internal+Status+Page+for+HK2+API+Changes



 Comments   
Comment by tbeerbower [ 01/May/12 ]

Replace org.jvnet.hk2.annotations.Inject with javax.inject.Inject.

Committed revision 53749.

Comment by tbeerbower [ 03/May/12 ]

Replace org.jvnet.hk2.annotations.Inject with javax.inject.Inject for constructor injection.

Committed revision 53798.

Comment by tbeerbower [ 03/May/12 ]

Replace org.jvnet.hk2.annotations.Inject with javax.inject.Inject for constructor injection with @Optional parameter.

Committed revision 53803.

Comment by jwells [ 18/Feb/13 ]

Fixed in April

Generated at Fri Mar 06 21:43:56 UTC 2015 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.