June 2012 - weld-issues - Jboss List Archives

[JBoss JIRA] (WELD-1140) Dependent scoped instances injected into observer method parameters are not destroyed for non-dependent reciever

by Martin Kouba (JIRA)

Martin Kouba created WELD-1140: ---------------------------------- Summary: Dependent scoped instances injected into observer method parameters are not destroyed for non-dependent reciever Key: WELD-1140 URL: https://issues.jboss.org/browse/WELD-1140 Project: Weld Issue Type: Bug Affects Versions: 2.0.0.Alpha2, 1.1.5.Final Reporter: Martin Kouba Dependent scoped contextual instances injected into method parameters of an observer method are not destroyed when the invocation completes in case of reciever itself is not dependent scoped. Problematic code: {{org.jboss.weld.event.ObserverMethodImpl.sendEvent(T, Object, CreationalContext<?>)}}. See also CDI TCK 1.1 test: https://github.com/jboss/cdi-tck/blob/master/impl/src/main/java/org/jboss... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

2
5
0 / 0

[JBoss JIRA] (WELD-1103) EJB using CMT demarcation with an injection point of type UserTransaction is not detected as definition error

by Martin Kouba (JIRA)

Martin Kouba created WELD-1103: ---------------------------------- Summary: EJB using CMT demarcation with an injection point of type UserTransaction is not detected as definition error Key: WELD-1103 URL: https://issues.jboss.org/browse/WELD-1103 Project: Weld Issue Type: Bug Reporter: Martin Kouba CDI spec *3.7. Additional built-in beans* states: "If a Java EE component class has an injection point of type UserTransaction and qualifier @Default, and may not validly make use of the JTA UserTransaction according to the Java EE platform specification, the container automatically detects the problem and treats it as a definition error." ... and EJB 3.1 spec states: *13.3.4 Enterprise Beans Using Container-Managed Transaction Demarcation* "The enterprise bean's business methods, message listener methods, business method interceptor meth- ods, lifecycle callback interceptor methods, or timeout callback methods must not attempt to obtain or use the javax.transaction.UserTransaction interface. ..." *16.12 UserTransaction Interface* "The container must make the UserTransaction interface available to the enterprise beans that are allowed to use this interface (only session and message-driven beans with bean-managed transaction demarcation are allowed to use this interface) either through injection using the Resource annotation or in JNDI under the name java:comp/UserTransaction, in addition to through the EJBContext interface. ..." -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

2
6
0 / 0

[JBoss JIRA] (WELD-1138) Interceptor bindings defined on stereotype not working for session beans

by Martin Kouba (JIRA)

Martin Kouba created WELD-1138: ---------------------------------- Summary: Interceptor bindings defined on stereotype not working for session beans Key: WELD-1138 URL: https://issues.jboss.org/browse/WELD-1138 Project: Weld Issue Type: Bug Reporter: Martin Kouba -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

2
6
0 / 0

[JBoss JIRA] (WELD-1088) Resource definition which specifies an EL name should be definition error

by Martin Kouba (JIRA)

Martin Kouba created WELD-1088: ---------------------------------- Summary: Resource definition which specifies an EL name should be definition error Key: WELD-1088 URL: https://issues.jboss.org/browse/WELD-1088 Project: Weld Issue Type: Bug Affects Versions: 2.0.0.Alpha1, 1.1.5.Final Reporter: Martin Kouba See "3.6.1. Declaring a resource" and TCK test *org.jboss.cdi.tck.tests.implementation.simple.resource.broken.name.ResourceDefinitionWithNameTest*. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

2
5
0 / 0

[JBoss JIRA] (WELD-1139) Business method interceptor bindings do not include bindings declared as meta-annotations of other interceptor bindings recursively

by Martin Kouba (JIRA)

Martin Kouba created WELD-1139: ---------------------------------- Summary: Business method interceptor bindings do not include bindings declared as meta-annotations of other interceptor bindings recursively Key: WELD-1139 URL: https://issues.jboss.org/browse/WELD-1139 Project: Weld Issue Type: Bug Affects Versions: 2.0.0.Alpha2, 1.1.5.Final Reporter: Martin Kouba It seems that only one level of inheritance is taken into account. The problem is likely in {{Interceptors.flattenInterceptorBindings(BeanManagerImpl, Collection<Annotation>, boolean, boolean)}} or {{InterceptorBindingModel}}. {quote} 9.5. Interceptor resolution: For a business method or EJB timeout method, the interceptor bindings include the interceptor bindings declared or inherited by the bean at the class level, including, recursively, interceptor bindings declared as meta-annotations of other interceptor bindings and stereotypes, together with all interceptor bindings declared at the method level, including, recursively, interceptor bindings declared as meta-annotations of other interceptor bindings. {quote} See also CDI TCK 1.1 test: https://github.com/jboss/cdi-tck/blob/master/impl/src/main/java/org/jboss... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

2
6
0 / 0

[JBoss JIRA] (WELD-992) Event of type ProcessObserverMethod not fired while adding observer method via AfterBeanDiscovery

by Martin Kouba (Created) (JIRA)

Event of type ProcessObserverMethod not fired while adding observer method via AfterBeanDiscovery ------------------------------------------------------------------------------------------------- Key: WELD-992 URL: https://issues.jboss.org/browse/WELD-992 Project: Weld Issue Type: Bug Components: Bootstrap and Metamodel API, Events Affects Versions: 1.1.2.Final Reporter: Martin Kouba CDI 1.0 *11.5.2. AfterBeanDiscovery event* states: "addObserverMethod() fires an event of type ProcessObserverMethod containing the given ObserverMethod and then registers the ObserverMethod with the container, thereby making it available for event." No event of type ProcessObserverMethod is fired when adding new observer method via *javax.enterprise.inject.spi.AfterBeanDiscovery.addObserverMethod(ObserverMethod<?>)*. However the new observer method is registered correctly. Refer to CDI TCK test [1]. [1] https://github.com/jboss/cdi-tck/blob/master/impl/src/main/java/org/jboss... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

3
6
0 / 0

[JBoss JIRA] (WELD-1071) @Specialized disposer method not recognized as a definition error

by Jozef Hartinger (JIRA)

Jozef Hartinger created WELD-1071: ------------------------------------- Summary: @Specialized disposer method not recognized as a definition error Key: WELD-1071 URL: https://issues.jboss.org/browse/WELD-1071 Project: Weld Issue Type: Bug Components: Producers (Methods, Fields and Disposers) Affects Versions: 2.0.0.Alpha1 Reporter: Jozef Hartinger Assignee: Jozef Hartinger Fix For: 2.0.0.Alpha2 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
5
0 / 0

[JBoss JIRA] Created: (WELD-975) Programmatic lookup with @New qualifier not working

by Martin Kouba (JIRA)

Programmatic lookup with @New qualifier not working --------------------------------------------------- Key: WELD-975 URL: https://issues.jboss.org/browse/WELD-975 Project: Weld Issue Type: Bug Affects Versions: 1.1.2.Final Environment: JBoss AS7 TestNG Arquillian CR5 Reporter: Martin Kouba According to spec: "...the @New qualifier may be used, allowing the application to obtain a @New qualified bean, as defined in Section 3.12, @New qualified beans" (CDI 1.0; chapter 5.6. Programmatic lookup). However using programmatic lookup with @New qualifier like: {code} @Inject @New Instance<Foo> foo; {code} results in: {code} org.jboss.weld.exceptions.UnsatisfiedResolutionException: WELD-001308 Unable to resolve any beans for Types: [class org.jboss.cditck.arquillian.instance.Foo]; Bindings: [@javax.enterprise.inject.New(value=org.jboss.cditck.arquillian.instance.Foo.class)] {code} after trying to obtain reference via get() method. Following code works ok: {code} @Inject @New Foo foo; {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

5
10
0 / 0

[JBoss JIRA] Created: (WELD-458) Interceptor for lifecycle callback with binding type @Target({TYPE, METHOD}) not detected as definition error

by Ondrej Skutka (JIRA)

Interceptor for lifecycle callback with binding type @Target({TYPE, METHOD}) not detected as definition error ------------------------------------------------------------------------------------------------------------- Key: WELD-458 URL: https://jira.jboss.org/jira/browse/WELD-458 Project: Weld Issue Type: Bug Components: Interceptors and Decorators Affects Versions: 1.0.1.Final Reporter: Ondrej Skutka Spec says: An interceptor for lifecycle callbacks may only declare interceptor binding types that are defined as @Target(TYPE). If an interceptor for lifecycle callbacks declares an interceptor binding type that is defined @Target({TYPE, METHOD}), the con- tainer automatically detects the problem and treats it as a definition error. org.jboss.jsr299.tck.tests.interceptors.definition.broken.interceptorForLifecycleTargetMethod.InterceptorForLifecycleTargetMethodTest In the TCK trunk -- 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

11 years, 8 months

6
14
0 / 0

[JBoss JIRA] (WELD-1152) Report of WELD-001443 doesn't identify source of dependency, making diagnosis harder

by Craig Ringer (JIRA)

11 years, 8 months

4
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues June 2012