[
https://issues.jboss.org/browse/CDI-4?page=com.atlassian.jira.plugin.syst...
]
Mike Brock edited comment on CDI-4 at 5/9/11 3:41 PM:
------------------------------------------------------
_Mike, can you impl your solution on top of Jason's proposal?_
Most likely. However, it's probably not something we could target in our own client
CDI stuff. So if the {{@Before}} {{@After}} stuff was not standardized, we'd be forced
to couple our stuff to a specific extension. That's the only downside for us.
It seems to me that, while not necessarily a problem for the majority, we should strongly
consider if this is a minority we should ignore. My opinion is that, while at any given
time this is a minority problem, the majority will probably run into it at some point or
another.
was (Author: cbrock):
_Mike, can you impl your solution on top of Jason's proposal?_
Most likely.
Need a way to provide ordering for Event observers (@Observes)
--------------------------------------------------------------
Key: CDI-4
URL:
https://issues.jboss.org/browse/CDI-4
Project: CDI Specification Issues
Issue Type: Feature Request
Components: Events, Portable Extensions
Affects Versions: 1.0
Environment: All
Reporter: Lincoln Baxter III
Assignee: Mike Brock
Fix For: TBD
There needs to be a way to specify some kind of ordering for Event observers.
Understandably, this is somewhat counter-intuitive to the general concept of observing an
event, but there is going to be need for this in an upcoming JBoss project. While it can
be done manually, it might be nice to have a built-in API.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira