Issue Details (XML | Word | Printable)

Key: GLASSFISH-18673
Type: Task Task
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: jwells
Reporter: tbeerbower
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
glassfish

Use JSR 330 annotations in GlassFish Cloud

Created: 01/May/12 07:37 PM   Updated: 18/Feb/13 09:00 PM   Resolved: 18/Feb/13 09:00 PM
Component/s: None
Affects Version/s: None
Fix Version/s: None

Time Tracking:
Not Specified

Tags:
Participants: jwells and tbeerbower


 Description  « Hide

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