December 2010 - weld-issues - Jboss List Archives

[JBoss JIRA] Created: (CDI-21) Support PostConstruct callbacks in Extension class

by Sivakumar Thyagarajan (JIRA)

Support PostConstruct callbacks in Extension class -------------------------------------------------- Key: CDI-21 URL: https://jira.jboss.org/browse/CDI-21 Project: CDI Specification Issues Issue Type: Feature Request Affects Versions: 1.0 Reporter: Sivakumar Thyagarajan Priority: Minor It is sometimes useful to get to know after a portable extension class has been instantiated, so that the state of the Extension could be initialized [ie not establishing state in the constructor and having it called twice when the Extension is proxied]. Though the 1.0 specification does not require this, it would be useful to support @PostConstruct callback on Extension class in the next version of the specification. Please see https://jira.jboss.org/browse/WELD-713 for additional information on this issue. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (WELD-717) @Observes(propagate = false) - stop event propagation after being handled by an observer

by Walter White (JIRA)

@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

13 years, 11 months

2
3
0 / 0

[JBoss JIRA] Created: (CDI-19) Ordering execution on Extensions

by Robson Saraiva Ximenes (JIRA)

Ordering execution on Extensions -------------------------------- Key: CDI-19 URL: https://jira.jboss.org/browse/CDI-19 Project: CDI Specification Issues Issue Type: Feature Request Components: Specification Affects Versions: 1.1 Reporter: Robson Saraiva Ximenes Priority: Minor I believe the cdi portable extension could have the load order of extensions the same as it is registered; It is possible that one extension expect some previous preparation of beans from another extension -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

2
2
0 / 0

[JBoss JIRA] Created: (CDI-16) Improve EE 6 Managed Bean integration

by Pete Muir (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

13 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (CDI-15) Relax @Target annotation for CDI Scopes and Qualifiers

by Stuart Douglas (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

13 years, 11 months

2
2
0 / 0

[JBoss JIRA] Created: (CDI-14) Add instance() method to BeanManager

by Pete Muir (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

13 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (CDI-13) Add ability to injection InjectionPoint into a decorator

by Pete Muir (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

13 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (CDI-12) Specifically exclude methods inherited from java.lang.Object from the list of business method invocations

by Marius Bogoevici (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

13 years, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (CDI-11) cdi-api lists el-api as optional in pom, but is required by api

by Aslak Knutsen (JIRA)

cdi-api lists el-api as optional in pom, but is required by api --------------------------------------------------------------- Key: CDI-11 URL: https://jira.jboss.org/browse/CDI-11 Project: CDI Specification Issues Issue Type: Bug Affects Versions: 1.0 Reporter: Aslak Knutsen ElResolver from el-api is a part of cdi-api's BeanManager interface, but the cdi-api pom lists el-api as optional. http://repo2.maven.org/maven2/javax/enterprise/cdi-api/1.0-SP1/cdi-api-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

13 years, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (WELD-465) Interceptors are not applied to custom bean types

by Stuart Douglas (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

13 years, 11 months

3
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues December 2010