This repository was archived by the owner on Jan 30, 2019. It is now read-only.
Repository navigation
This repository was archived by the owner on Jan 30, 2019. It is now read-only.
Prioritizing @Singleton & @WebServlet with @Priority #17
Description
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
glassfishrobot commentedon Dec 17, 2012
Reported by agoncal
glassfishrobot commentedon Jan 24, 2013
ldemichiel said:
Yes, please feel free to raise this issue with those expert groups when we enter Java EE 8.
glassfishrobot commentedon Nov 3, 2014
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.
glassfishrobot commentedon Nov 4, 2014
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.
glassfishrobot commentedon Nov 16, 2014
agoncal said:
As discussed with Linda, here is how she rephrase it :
I think we should, at least, do 1) but of course 2) will be better
glassfishrobot commentedon Apr 25, 2017
This issue was imported from java.net JIRA JAVAEE_SPEC-17