July 2012 - weld-issues - Jboss List Archives

[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

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

12 years, 5 months

3
2
0 / 0

[JBoss JIRA] (WELD-1147) Update to zanata-maven-plugin 1.6.0, update readme file

by Sean Flanigan (JIRA)

Sean Flanigan created WELD-1147: ----------------------------------- Summary: Update to zanata-maven-plugin 1.6.0, update readme file Key: WELD-1147 URL: https://issues.jboss.org/browse/WELD-1147 Project: Weld Issue Type: Patch Reporter: Sean Flanigan The old version of the Zanata plugin has been having some trouble when pulling translations from translate.jboss.org (possibly because one of the dependencies got upgraded). This pull request upgrades to the latest, v 1.6.0, and also brings the readme file up to date. -- 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, 5 months

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

12 years, 5 months

3
3
0 / 0

[JBoss JIRA] (WELD-1166) ProcessBean getAnnotated returns null for built-in beans

by Marek Schmidt (JIRA)

12 years, 5 months

2
1
0 / 0

[JBoss JIRA] (WELD-1165) CLONE - Weld - Deadlock between Weld AbstractContext session/application contexts creationLock

by Marek Schmidt (JIRA)

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WELD-1164) CLONE - Weld - Deadlock between SFSB Synchronization lock and Weld AbstractContext session context lock

by Marek Schmidt (JIRA)

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WELD-1163) CLONE - Weld - Long running producer called multiple times in the same context

by Marek Schmidt (JIRA)

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WELD-51) Extract Reflection layer into SPI to allow container to provide an enhanced (faster) impl

by Jozef Hartinger (JIRA)

12 years, 5 months

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

12 years, 5 months

4
10
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues July 2012