[ https://issues.jboss.org/browse/CDI-39?page=com.atlassian.jira.plugin.sys... ]
Pete Muir updated CDI-39:
-------------------------
Fix Version/s: TBD
> Add a standard format for defining metadata about extensions
> ------------------------------------------------------------
>
> Key: CDI-39
> URL: https://issues.jboss.org/browse/CDI-39
> Project: CDI Specification Issues
> Issue Type: Feature Request
> Components: Portable Extensions
> Affects Versions: 1.0
> Reporter: Pete Muir
> Fix For: TBD
>
>
> e.g. add optional name, description and version fields to an optional annotation. Makes it easy for modules to track what is being loaded
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ https://issues.jboss.org/browse/CDI-32?page=com.atlassian.jira.plugin.sys... ]
Pete Muir updated CDI-32:
-------------------------
Fix Version/s: TBD
> A method of controlling event ordering
> --------------------------------------
>
> Key: CDI-32
> URL: https://issues.jboss.org/browse/CDI-32
> Project: CDI Specification Issues
> Issue Type: Feature Request
> Components: Events
> Affects Versions: 1.0
> Reporter: Nicklas Karlsson
> Fix For: TBD
>
>
> It would be handy to have a way of controlling the order in which synchronous events are being called
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ https://issues.jboss.org/browse/CDI-4?page=com.atlassian.jira.plugin.syst... ]
Pete Muir updated CDI-4:
------------------------
Fix Version/s: TBD
> 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
> 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
[ https://issues.jboss.org/browse/CDI-52?page=com.atlassian.jira.plugin.sys... ]
Pete Muir updated CDI-52:
-------------------------
Fix Version/s: TBD
> Make it clearer that an InjectionPoint injected into a disposer method refers to the producer method bean and not to the declaring bean
> ---------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CDI-52
> URL: https://issues.jboss.org/browse/CDI-52
> Project: CDI Specification Issues
> Issue Type: Bug
> Components: Beans
> Affects Versions: 1.0
> Reporter: Pete Muir
> Fix For: TBD
>
>
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ https://issues.jboss.org/browse/CDI-74?page=com.atlassian.jira.plugin.sys... ]
Pete Muir updated CDI-74:
-------------------------
Fix Version/s: TBD
(was: 1.1)
> State explicitely that Decorators and Interceptors of must be implemented via subclassing
> -----------------------------------------------------------------------------------------
>
> Key: CDI-74
> URL: https://issues.jboss.org/browse/CDI-74
> Project: CDI Specification Issues
> Issue Type: Feature Request
> Components: Decorators, Interceptors
> Affects Versions: 1.0
> Reporter: Marius Bogoevici
> Fix For: TBD
>
>
> Subclassing should be mandatory for Decorators and Interceptors of managed beans which are not session beans (no restrictions in the case of the latter).
> This ensures that:
> - fields on pseudo scoped managed beans are accessible
> - there's no restriction on what kinds of constructors may a managed bean have
> - no extra bean instances are created when a managed bean is created
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira