Description

glassfishrobot

opened on Dec 17, 2012

Issue body actions

Following the thread http://java.net/projects/javaee-spec/lists/users/archive/2012-12/message/17

@priority is used to priorityze interceptors in Java EE 7. It would be interesting to spread this feature to other components in Java EE 8, for example @singleton & @WebServlet.

@Singleton
@Startup
@Priority(100)
public class MyVeryFirstSingleton {}

@Singleton
@Startup
@Priority(4500)
public class MyVeryLastSingleton {}

Activity

1. glassfishrobot commented on Dec 17, 2012

   

   glassfishrobot

   on Dec 17, 2012

   Author

   More actions

   Reported by agoncal
2. glassfishrobot commented on Jan 24, 2013

   

   glassfishrobot

   on Jan 24, 2013

   Author

   More actions

   ldemichiel said:
   Yes, please feel free to raise this issue with those expert groups when we enter Java EE 8.
3. glassfishrobot commented on Nov 3, 2014

   

   glassfishrobot

   on Nov 3, 2014

   Author

   More actions

   ldemichiel said:
   Just to clarify.... Did you mean for example prioritizing amongst the startup of other singletons, or prioritizing more globally (i.e., the whole startup order of the application)? If the former (i.e., prioritizing singletons amongst singletons; etc.), could you please re-file the appropriate issues for the individual expert groups.
4. glassfishrobot commented on Nov 4, 2014

   

   glassfishrobot

   on Nov 4, 2014

   Author

   More actions

   agoncal said:
   The title of the JIRA is maybe not appropriate, as it could have been "Being able to prioritize Java EE components when ordered is needed". So yes, this topic is first to be debated in the Java EE expert group, and then push it to the other specs.
5. glassfishrobot commented on Nov 16, 2014

   

   glassfishrobot

   on Nov 16, 2014

   Author

   More actions

   agoncal said:
   As discussed with Linda, here is how she rephrase it :

   (1) Various expert groups should evaluate how they can leverage
   the @priority annotation. For example, EJB could use it to
   order the startup of singleton beans; Servlet could use it to
   order the invocation of Filters;.... [I.e., the annotation would be
   used to order within particular managed classes, beyond those we
   already support its use on.]

   OR

   (2) @priority could be used to prioritize the startup order of
   the application. For example, EJB singletons would be started
   before the JPA EntityManagerFactory was initialized, ....
   [I.e., the annotation would be used to order more globally within
   the application.]

   I think we should, at least, do 1) but of course 2) will be better
6. glassfishrobot commented on Apr 25, 2017

   

   glassfishrobot

   on Apr 25, 2017

   Author

   More actions

   This issue was imported from java.net JIRA JAVAEE_SPEC-17
7. glassfishrobot

   added

   Type: New Feature

   Priority: Major

   java_ee_8

   on Apr 25, 2017
8. glassfishrobot

   assigned

   ldemichiel

   on Apr 25, 2017

Issue actions