August 2012 - weld-issues - Jboss List Archives

[JBoss JIRA] (WELD-1052) Unproxyable bean type check too strict

by Jozef Hartinger (JIRA)

Jozef Hartinger created WELD-1052: ------------------------------------- Summary: Unproxyable bean type check too strict Key: WELD-1052 URL: https://issues.jboss.org/browse/WELD-1052 Project: Weld Issue Type: Bug Components: Proxies Affects Versions: 1.1.5.Final Reporter: Jozef Hartinger Assignee: Jozef Hartinger Fix For: 2.0.0.Alpha2 According to the specification, a deployment that contains the following bean: {code:JAVA} public interface FooInterface { } @ApplicationScoped public final class Foo implements FooInterface { } {code} is valid as long as there is no injection point injecting Foo directly. The following injection point is valid: {code:JAVA} @Inject private FooInterface foo; {code} -- 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

12 years, 3 months

1
5
0 / 0

[JBoss JIRA] (WELD-1054) Parameterized bean type with actual type argument is assignable to a raw required type

by Martin Kouba (JIRA)

Martin Kouba created WELD-1054: ---------------------------------- Summary: Parameterized bean type with actual type argument is assignable to a raw required type Key: WELD-1054 URL: https://issues.jboss.org/browse/WELD-1054 Project: Weld Issue Type: Bug Reporter: Martin Kouba *5.2.3. Assignability of raw and parameterized types*: "A parameterized bean type is considered assignable to a raw required type if the raw types are identical and all type parameters of the bean type are either unbounded type variables or java.lang.Object." See *org.jboss.cdi.tck.tests.lookup.typesafe.resolution.parameterized.AssignabilityOfRawAndParameterizedTypesTest.testAssignabilityToRawType()* -- 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

12 years, 3 months

3
7
0 / 0

[JBoss JIRA] (WELD-1060) Any bean type with identical raw type is assignable to a parameterized required type with type variable parameter

by Martin Kouba (JIRA)

Martin Kouba created WELD-1060: ---------------------------------- Summary: Any bean type with identical raw type is assignable to a parameterized required type with type variable parameter Key: WELD-1060 URL: https://issues.jboss.org/browse/WELD-1060 Project: Weld Issue Type: Bug Reporter: Martin Kouba *5.2.3. Assignability of raw and parameterized types*: "A parameterized bean type is considered assignable to a parameterized required type if they have identical raw type and for each parameter * ... * the required type parameter and the bean type parameter are both type variables and the upper bound of the required type parameter is assignable to the upper bound, if any, of the bean type parameter." See *org.jboss.cdi.tck.tests.lookup.typesafe.resolution.parameterized.AssignabilityOfRawAndParameterizedTypesTest.testAssignabilityOfParameterizedTypeWithTypeVariablesToParameterizedTypeTypeVariable()* -- 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

12 years, 3 months

3
5
0 / 0

[JBoss JIRA] (WELD-1117) Disposer method check too strict

by Jozef Hartinger (JIRA)

Jozef Hartinger created WELD-1117: ------------------------------------- Summary: Disposer method check too strict Key: WELD-1117 URL: https://issues.jboss.org/browse/WELD-1117 Project: Weld Issue Type: Bug Components: Producers (Methods, Fields and Disposers) Affects Versions: 2.0.0.Alpha2 Reporter: Jozef Hartinger Assignee: Jozef Hartinger Fix For: 2.0.0.Alpha3 {code:JAVA} if (!getEnhancedAnnotated().getEnhancedParameters().get(0).isAnnotationPresent(Disposes.class)) { throw new DefinitionException(DISPOSE_NOT_FIRST_PARAM, disposalMethodInjectionPoint); } {code} in DisposalMethod.java is not a valid check. -- 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

12 years, 3 months

1
4
0 / 0

[JBoss JIRA] (WELD-1168) pastecode example fails to deploy with WELD-001451 javax.transaction.UserTransaction cannot be injected into an enterprise bean with container-managed transactions

by Marek Schmidt (JIRA)

12 years, 3 months

2
3
0 / 0

[JBoss JIRA] (WELD-991) Incorrect check of bean type when obtaining contextual reference via BeanManager#getReference()

by Martin Kouba (Created) (JIRA)

Incorrect check of bean type when obtaining contextual reference via BeanManager#getReference() ----------------------------------------------------------------------------------------------- Key: WELD-991 URL: https://issues.jboss.org/browse/WELD-991 Project: Weld Issue Type: Bug Affects Versions: 1.1.2.Final Reporter: Martin Kouba CDI 1.0 section "11.3.1 Obtaining a contextual reference for a bean" states: "If the given type is not a bean type of the given bean, an IllegalArgumentException is thrown." However no such exception is thrown. Refer to CDI TCK test [1]. After inspecting the source code I suppose the problem is probably related to following part of *org.jboss.weld.manager.BeanManagerImpl.getReference(Bean<?>, Type, CreationalContext<?>)*: {code} if (!Reflections.isAssignableFrom(bean.getTypes(), beanType)) { throw new IllegalArgumentException(SPECIFIED_TYPE_NOT_BEAN_TYPE, beanType, bean ); } {code} All beans have the bean type *java.lang.Object* (2.2. Bean types) - since java.lang.Object is assignable from any class *Reflections.isAssignableFrom(bean.getTypes(), beanType)* will always return true. [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

12 years, 3 months

6
8
0 / 0

[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

12 years, 3 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

12 years, 3 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

12 years, 3 months

2
6
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

12 years, 3 months

2
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues August 2012