April 2012 - weld-issues - Jboss List Archives

[JBoss JIRA] Created: (WELD-930) Producer is made an alternative if the declaring bean class is an alternative

by Alexey Kazakov (JIRA)

Producer is made an alternative if the declaring bean class is an alternative ----------------------------------------------------------------------------- Key: WELD-930 URL: https://issues.jboss.org/browse/WELD-930 Project: Weld Issue Type: Bug Components: Producers (Methods, Fields and Disposers) Affects Versions: 1.1.0.Final Reporter: Alexey Kazakov I'm looking at examples from https://github.com/pmuir/jboss-as-developer-guide/tree/master/quickstarts There is org.jboss.as.quickstarts.login.EJBUserManager: {code:title=org.jboss.as.quickstarts.login.EJBUserManager|borderStyle=solid} ... @Named("userManager") @RequestScoped @Alternative @Stateful public class EJBUserManager implements UserManager { ... @Produces @Named @RequestScoped public List<User> getUsers() throws Exception { ... } ... } {code} And there is also another bean org.jboss.as.quickstarts.login.ManagedBeanUserManager: {code:title=org.jboss.as.quickstarts.login.ManagedBeanUserManager|borderStyle=solid} ... @Named("userManager") @RequestScoped public class ManagedBeanUserManager implements UserManager { @SuppressWarnings("unchecked") @Produces @Named @RequestScoped public List<User> getUsers() throws Exception { ... } ... } {code} This code works in Weld even if EJBUserManager.getUsers() is not annotated @Alternative. But regarding the spec such a method has an ambiguous EL name "users": {quote} 5.3.1. Ambiguous EL names An ambiguous EL name exists in an EL expression when an EL name resolves to multiple beans. When an ambiguous EL name exists, the container attempts to resolve the ambiguity. If any of the beans are alternatives, the container eliminates all beans that are not alternatives, *except for producer methods and fields of beans that are alternatives*. If there is exactly one bean remaining, the container will select this bean, and the ambiguous EL name is called resolvable. {quote} There is a comment from Pete Muir: {quote} This looks to me like a bug in Weld (one that crept in from a pre-final spec revision) - that it checks if the declaring bean class is an alternative, and if it is, makes the producer an alternative. Can you file a WELD issue for this? I'll update the quickstart to explicitly make the producer an alternative. Pete {quote} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

5
8
0 / 0

[JBoss JIRA] (WELD-1094) BeanManager#createInjectionTarget - IllegalArgumentException not thrown if there is a definition error associated with any injection point

by Martin Kouba (JIRA)

Martin Kouba created WELD-1094: ---------------------------------- Summary: BeanManager#createInjectionTarget - IllegalArgumentException not thrown if there is a definition error associated with any injection point Key: WELD-1094 URL: https://issues.jboss.org/browse/WELD-1094 Project: Weld Issue Type: Bug Affects Versions: 2.0.0.Alpha1 Reporter: Martin Kouba *11.3.19. Obtaining an InjectionTarget for a class*: "The method BeanManager.createInjectionTarget() returns a container provided implementation of InjectionTarget for a given AnnotatedType or throws an IllegalArgumentException if there is a definition error associated with any injection point of the type." See TCK 1.1 test: *org.jboss.cdi.tck.tests.extensions.beanManager.BeanManagerTest.testObtainingInjectionTargetWithDefinitionError()* -- 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, 9 months

2
4
0 / 0

[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

11 years, 9 months

1
5
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

11 years, 9 months

3
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

11 years, 9 months

3
7
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

11 years, 9 months

1
4
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

11 years, 9 months

6
8
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, 9 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, 9 months

2
5
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, 9 months

3
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues April 2012