@Observes(propagate = false) - stop event propagation after being handled by an observer
----------------------------------------------------------------------------------------
Key: WELD-717
URL: https://jira.jboss.org/browse/WELD-717
Project: Weld
Issue Type: Feature Request
Components: Events
Affects Versions: 1.0.1.Final
Environment: any
Reporter: Walter White
I would like to have the ability to stop event propagation after it is handled by any observer only for certain situations. Is it possible to add a property to the annotation indicating whether the propagation should continue after being handled by the observer? Alternatively, would it be more concise to add a qualifier annotation which specifies the propagation.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Improve EE 6 Managed Bean integration
-------------------------------------
Key: CDI-16
URL: https://jira.jboss.org/browse/CDI-16
Project: CDI Specification Issues
Issue Type: Feature Request
Components: Specification
Reporter: Pete Muir
Fix For: 1.1
Try to work out if we can improve on this.
At least, we should clarify what happens if a CDI managed bean is annotated with @ManagedBean
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Relax @Target annotation for CDI Scopes and Qualifiers
------------------------------------------------------
Key: CDI-15
URL: https://jira.jboss.org/browse/CDI-15
Project: CDI Specification Issues
Issue Type: Feature Request
Components: Specification
Affects Versions: 1.0
Reporter: Stuart Douglas
In some cases it may make sense to apply a scope or qualifier in a place that was not envisaged by the spec but that would be useful for a portable extension.
For example, the @Constructs extension described at
http://www.seamframework.org/Weld/PortableExtensionsPackage#H-BeanDeclara...
is not possible because scopes and qualifiers can not be placed on constructors
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Add instance() method to BeanManager
------------------------------------
Key: CDI-14
URL: https://jira.jboss.org/browse/CDI-14
Project: CDI Specification Issues
Issue Type: Feature Request
Components: Specification
Affects Versions: 1.0
Reporter: Pete Muir
Fix For: 1.1
Currently obtaining a contextual reference is quite a complex operation, adding a method like:
Instance<Object> instance();
would make it much easier.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Add ability to injection InjectionPoint into a decorator
--------------------------------------------------------
Key: CDI-13
URL: https://jira.jboss.org/browse/CDI-13
Project: CDI Specification Issues
Issue Type: Feature Request
Components: Specification
Affects Versions: 1.0
Reporter: Pete Muir
Fix For: 1.1
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Specifically exclude methods inherited from java.lang.Object from the list of business method invocations
---------------------------------------------------------------------------------------------------------
Key: CDI-12
URL: https://jira.jboss.org/browse/CDI-12
Project: CDI Specification Issues
Issue Type: Feature Request
Components: Specification
Affects Versions: 1.0
Reporter: Marius Bogoevici
Priority: Optional
Without this specific exclusion, there is a theoretical possibility to treat these methods as business method invocations.
- they are defined on the object;
- will be present on the contextual reference;
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Interceptors are not applied to custom bean types
-------------------------------------------------
Key: WELD-465
URL: https://jira.jboss.org/jira/browse/WELD-465
Project: Weld
Issue Type: Bug
Reporter: Stuart Douglas
Beans added through the SPI do not have interceptors applied.
Even though bean does not have a getInterceptorBindings() method, interceptors applied to stereotypes should still work.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Need a way to provide ordering for Event observers (@Observes)
--------------------------------------------------------------
Key: CDI-4
URL: https://jira.jboss.org/browse/CDI-4
Project: CDI Specification Issues
Issue Type: Feature Request
Environment: All
Reporter: Lincoln Baxter III
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.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira