[
https://issues.jboss.org/browse/FORGE-1498?page=com.atlassian.jira.plugin...
]
Lincoln Baxter III closed FORGE-1498.
-------------------------------------
Resolution: Won't Fix
I don't think that we should implement this. If ordering is required, it should be
enforced by the interface of the Service being requested. This isn't something that we
should try to do in Furnace. Re-open if you really disagree :)
Allow ordering in the lookup of services in AddonRegistry
---------------------------------------------------------
Key: FORGE-1498
URL:
https://issues.jboss.org/browse/FORGE-1498
Project: Forge
Issue Type: Enhancement
Components: Brainstorming, Furnace (Container)
Affects Versions: 2.0.0.CR1
Reporter: George Gastaldi
Fix For: 2.x Future
Some services may require to be executed before others. It would be nice if the container
could order these services while an iteraction of an {{Imported}} object happens. This
ordering may happen based on an annotation or an interface.
Eg: When an {{UIContextListener}} is returned from an {{Imported}}, the
{{CommandScopedContext}} should be fired first, to allow {{@CommandScoped}} objects to
exist before other UIContextListeners are fired.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira