The issue is regarding the order specified by the iterator returned in Imported.iterator(). In some scenarios, like the one described in the issue, the consumer is unaware of how to order the returned services.Not sure I really follow this issue. What is the problem? Service lookups just return objects, so activation order could be handled by the consumer.On Sat, Jan 25, 2014 at 9:37 PM, George Gastaldi (JIRA) <issues@jboss.org> wrote:George Gastaldi created FORGE-1498:
--------------------------------------
Summary: 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
_______________________________________________
forge-issues mailing list
forge-issues@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/forge-issues
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."_______________________________________________
forge-issues mailing list
forge-issues@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/forge-issues