April 2012 - weld-issues - Jboss List Archives

[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, 9 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, 9 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, 9 months

6
14
0 / 0

[JBoss JIRA] (WELD-1065) Ambiguous name validation should not cross visibility boundaries

by Jozef Hartinger (JIRA)

Jozef Hartinger created WELD-1065: ------------------------------------- Summary: Ambiguous name validation should not cross visibility boundaries Key: WELD-1065 URL: https://issues.jboss.org/browse/WELD-1065 Project: Weld Issue Type: Bug Affects Versions: 1.1.5.Final Reporter: Jozef Hartinger Assignee: Jozef Hartinger Fix For: 1.2.0.Beta1, 2.0.0.Alpha2 Caused by "additionalBeanDeploymentArchive" in the AS7 integration code that makes every two deployed beans transitively visible. -- 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

4
9
0 / 0

[JBoss JIRA] (CDITCK-263) UnproxyableManagedBeanTest should test runtime exception

by Martin Kouba (JIRA)

Martin Kouba created CDITCK-263: ----------------------------------- Summary: UnproxyableManagedBeanTest should test runtime exception Key: CDITCK-263 URL: https://issues.jboss.org/browse/CDITCK-263 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Martin Kouba Assignee: Martin Kouba Fix For: 1.1.0.CR1 Fix *org.jboss.jsr299.tck.tests.implementation.simple.lifecycle.unproxyable.UnproxyableManagedBeanTest* to test runtime exception (UnproxyableResolutionException) instead of deployment time exception (DefinitionException). -- 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
3
0 / 0

[JBoss JIRA] Created: (WELD-964) Unsatisfied dependency exception should differentiate between "class is not in classpath", "class is in classpath but not managed bean" and "class is in classpath and managed but not like that"

by Geoffrey De Smet (JIRA)

Unsatisfied dependency exception should differentiate between "class is not in classpath", "class is in classpath but not managed bean" and "class is in classpath and managed but not like that" ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: WELD-964 URL: https://issues.jboss.org/browse/WELD-964 Project: Weld Issue Type: Enhancement Reporter: Geoffrey De Smet Having an "unsatisfied dependency" can have several causes: - The jar is not in the classpath - The jar is in the classpath, but the beans.xml is not being picked up (for whatever reason, such as problems with WEB-INF/beans.xml on some containers) - The jar is in the classpath, the beans.xml is picked up but the qualifiers etc don't match. So, instead of just saying "unsatisfied dependency ...": it should say something like this: - Unsatisfied dependency ... and there is no concrete implementing class in the classpath. - Unsatisfied dependency ... and the concrete implementing class(es) are not loaded as managed beans through a beans.xml. - Unsatisfied dependency ... and none of the managed beans of the same type match. Note: spring's exceptions differentiate between these cases (they explicitly define their appContext.xml set, so case 2 is impossible and case 1 throws a "app context file not found" exception. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

3
2
0 / 0

[JBoss JIRA] (WELD-1045) ProcessBeanAttributes not fired for interceptors and decorators

by Martin Kouba (Created) (JIRA)

ProcessBeanAttributes not fired for interceptors and decorators --------------------------------------------------------------- Key: WELD-1045 URL: https://issues.jboss.org/browse/WELD-1045 Project: Weld Issue Type: Bug Reporter: Martin Kouba Assignee: Jozef Hartinger Fix For: 2.0.0.Alpha1 The spec (CDI 1.1) states: "The container must fire an event for each enabled bean, interceptor or decorator deployed in a bean archive, before registering the Bean object." However ProcessBeanAttributes is not fired for interceptors and decorators. Probably because of *BeanDeployerEnvironment.addInterceptor(InterceptorImpl<?>)* and *BeanDeployerEnvironment.addDecorator(DecoratorImpl<?>)* do not add intercetors and decorators bean to classBeanMap - the source of beans used in *org.jboss.weld.bootstrap.BeanDeployer.processBeans()*. -- 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, 10 months

3
3
0 / 0

[JBoss JIRA] (WELD-998) Alternative custom bean not available for injection in other custom bean

by Martin Kouba (Created) (JIRA)

Alternative custom bean not available for injection in other custom bean ------------------------------------------------------------------------ Key: WELD-998 URL: https://issues.jboss.org/browse/WELD-998 Project: Weld Issue Type: Bug Affects Versions: 1.1.2.Final Reporter: Martin Kouba Suppose we have extension that registers two custom beans (while observing AfterBeanDiscovery event). Custom bean A is alternative. Custom bean B is not alternative and has injection point with type A. This scenario causes deployment error: "WELD-001408 Unsatisfied dependencies...". It seems that *ProcessBean* event is not fired after calling *javax.enterprise.inject.spi.AfterBeanDiscovery.addBean(Bean<?>)* because *org.jboss.weld.manager.BeanManagerImpl.isBeanEnabled(Bean<?>)* resolves to false at the given moment. Nevertheless it is available for injection in "regular" beans after deployment validation (suppose custom bean B is not included). Note that if custom bean A#isAlternative() returns false, test passes. See TCK test: https://github.com/jboss/cdi-tck/tree/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, 10 months

4
10
0 / 0

[JBoss JIRA] (WELD-1120) Create better bootstrap configuration

by Jozef Hartinger (JIRA)

Jozef Hartinger created WELD-1120: ------------------------------------- Summary: Create better bootstrap configuration Key: WELD-1120 URL: https://issues.jboss.org/browse/WELD-1120 Project: Weld Issue Type: Task Affects Versions: 2.0.0.Alpha2 Reporter: Jozef Hartinger Assignee: Jozef Hartinger Fix For: 2.0.0.Alpha3 So that we can configure: * number of threads used for deployer * enable / disable ContainerLifecycleEventPreloader * enable / disable ConcurrentBeanDeployer / Validator * suppress ExecutorServices entirely (for GAE) -- 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, 10 months

1
1
0 / 0

[JBoss JIRA] (WELD-1115) UnserializableDependencyException with dependency on SLSB

by Marek Schmidt (JIRA)

Marek Schmidt created WELD-1115: ----------------------------------- Summary: UnserializableDependencyException with dependency on SLSB Key: WELD-1115 URL: https://issues.jboss.org/browse/WELD-1115 Project: Weld Issue Type: Bug Components: Bootstrap and Metamodel API Affects Versions: 2.0.0.Alpha2 Environment: AS 7.1.1.Final with Weld 2.0.0.Alpha2 Reporter: Marek Schmidt Assignee: Jozef Hartinger Fix For: 2.0.0.Alpha3 An application containing the following beans (among others) fails to deploy with org.jboss.weld.exceptions.UnserializableDependencyException. {code} @SessionScoped @Stateful public EjbGameBean implements Serializable { ... @Inject RandomStatelessEjb randomStatelessEjb; ... } {code} {code} @Stateless public class RandomStatelessEjb { @Inject @Random Instance<Integer> randomNumber; public int getRandom() { return randomNumber.get(); } } {code} It probably shouldn't require a @Stateless session bean to be Serializable. {noformat} JBAS014777: Services which failed to start: service jboss.deployment.unit."weld-clustering-tests.war".WeldService: org.jboss.msc.service.StartException in service jboss.deployment.unit."weld-clustering-tests.war".WeldService: org.jboss.weld.exceptions.UnserializableDependencyException: WELD-001413 The bean Session bean [class org.jboss.weld.tests.clustering.numberguess.decorator.EjbGameBean with qualifiers [@Default @Named @Any]; local interfaces are [GameLocal] declares passivating scope but has non-serializable dependency Session bean [class org.jboss.weld.tests.clustering.numberguess.decorator.RandomStatelessEjb with qualifiers [@Any @Default]; local interfaces are [RandomStatelessEjb] {noformat} -- 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, 10 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues April 2012