March 2012 - weld-issues - Jboss List Archives

[JBoss JIRA] (WELD-1087) CLONE - Double-checked locking in org.jboss.weld.util.BeansClosure#getClosure is a cause for NPE

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WELD-1087?page=com.atlassian.jira.plugin.... ] Stuart Douglas resolved WELD-1087. ---------------------------------- Resolution: Duplicate Issue This is actually a duplicate of WELD-1067, which is fixed upstream > CLONE - Double-checked locking in org.jboss.weld.util.BeansClosure#getClosure is a cause for NPE > ------------------------------------------------------------------------------------------------ > > Key: WELD-1087 > URL: https://issues.jboss.org/browse/WELD-1087 > Project: Weld > Issue Type: Bug > Affects Versions: 1.1.5.Final > Environment: N/A > Reporter: Anton Arhipov > Assignee: Stuart Douglas > Labels: cdi, jbossas_7.1, weld > > Application deployment fails with a following exception: > 05:33:26,201 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC00001: Failed to start service jboss.deployment.unit."exp-cdi-injectApplication.war".WeldService: org.jboss.msc.service.StartException in service jboss.deployment.unit."exp-cdi-injectApplication.war".WeldService: java.lang.NullPointerException > at org.jboss.as.weld.services.WeldService.start(WeldService.java:83) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_27] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_27] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_27] > Caused by: java.lang.NullPointerException > at org.jboss.weld.bootstrap.BeanDeployment.createBeans(BeanDeployment.java:194) > at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:336) > at org.jboss.as.weld.WeldContainer.start(WeldContainer.java:82) > at org.jboss.as.weld.services.WeldService.start(WeldService.java:76) > ... 5 more > Looking at the code that belongs to weld-core-1.1.5.AS71.Final, we can see the following at the lines 193-194 of BeanDeployment: > 193: BeansClosure closure = BeansClosure.getClosure(this.beanManager); > 194: closure.addEnvironment(this.beanDeployer.getEnvironment()); > Which leads to a conclusion that closure is null (the lines prior to the mentioned ones show that beanDeployer itself couldn't be null). > Looking into BeansClosure#getClosure(): > public static BeansClosure getClosure(BeanManagerImpl beanManager) > { > BeansClosure closure = (BeansClosure)closureMap.get(beanManager); > if (closure == null) { > synchronized (closureMap) { > if (!closureMap.containsKey(beanManager)) { > closure = new BeansClosure(); > for (Iterable beanManagers : BeanManagers.getAccessibleClosure(beanManager)) { > for (BeanManagerImpl accessibleBeanManager : beanManagers) { > closureMap.put(accessibleBeanManager, closure); > } > } > } > } > } > return closure; > } > To prevent race conditions, maybe it makes sense to reside the full method body into synchronized block. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (WELD-1070) WeldPhaseListener destroys conversation too soon

by Bernard Labno (JIRA)

Bernard Labno created WELD-1070: ----------------------------------- Summary: WeldPhaseListener destroys conversation too soon Key: WELD-1070 URL: https://issues.jboss.org/browse/WELD-1070 Project: Weld Issue Type: Bug Components: Conversations Affects Versions: 1.1.4.Final Environment: gentoo, java 1.6, AS7.1.0.Beta1, Seam 3.1.0.Final Reporter: Bernard Labno In JSF app when exception is thrown during RenderResponse phase then firstly there is a call to afterPhase and later to exception handlers. WeldPhaseListener.afterPhase is invoked before error handler (Seam Catch in my case). My error handler wants to promote conversation to long-running and do redirect to error page, but conversation context is not active anymore now. -- 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, 1 month

3
2
0 / 0

[JBoss JIRA] Created: (WELD-816) Adding interceptors and Decorators in the AfterBeanDiscovery event does not work

by Stuart Douglas (JIRA)

Adding interceptors and Decorators in the AfterBeanDiscovery event does not work -------------------------------------------------------------------------------- Key: WELD-816 URL: https://issues.jboss.org/browse/WELD-816 Project: Weld Issue Type: Bug Reporter: Stuart Douglas -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

4
9
0 / 0

[JBoss JIRA] Created: (WELD-853) @AroundInvoke annotations added by SPI are ignored

by Stuart Douglas (JIRA)

@AroundInvoke annotations added by SPI are ignored -------------------------------------------------- Key: WELD-853 URL: https://issues.jboss.org/browse/WELD-853 Project: Weld Issue Type: Bug Affects Versions: 1.1.0.Final Reporter: Stuart Douglas There should be a test for this however it has been reverted by this commit: https://github.com/weld/core/commit/562d55d27938f01b9f1a793f161540f681d51f47 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

5
7
0 / 0

[JBoss JIRA] (WELD-997) Custom implementation of Interceptor never invokedi

by Jozef Hartinger (Created) (JIRA)

Custom implementation of Interceptor never invokedi --------------------------------------------------- Key: WELD-997 URL: https://issues.jboss.org/browse/WELD-997 Project: Weld Issue Type: Bug Components: Interceptors and Decorators Affects Versions: 1.1.2.Final Reporter: Jozef Hartinger Fix For: 1.2.0.Beta1 -- 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, 1 month

8
9
0 / 0

[JBoss JIRA] (WELD-1075) Ambiguous dependencies when only one correct dependency exists

by Sebastian Graca (JIRA)

Sebastian Graca created WELD-1075: ------------------------------------- Summary: Ambiguous dependencies when only one correct dependency exists Key: WELD-1075 URL: https://issues.jboss.org/browse/WELD-1075 Project: Weld Issue Type: Bug Components: Resolution (Typesafe and by Name) Affects Versions: 1.1.4.Final, 1.1.1.Final Reporter: Sebastian Graca Attachments: testcase.zip Running attached application gives the error: WELD-001409 Ambiguous dependencies for type [Interface1<UUID, String>] with qualifiers [@Default] at injection point [[field] @Inject private test.Bean.dependency]. Possible dependencies [[Managed Bean [class test.ConcreteClass1] with qualifiers [@Any @Default], Managed Bean [class test.ConcreteClass2] with qualifiers [@Any @Default], Managed Bean [class test.ConcreteClass3] with qualifiers [@Any @Default]]] But only ConcreteClass3 has required type of Interface1<UUID, String> When ConcreteClass1 and ConcreteClass2 extens AbstractClass1 instead of AbstractClass2 everything works as expected. -- 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, 1 month

3
10
0 / 0

[JBoss JIRA] Created: (WELD-731) Bind BeanManager to JNDI when naming context is read/write (as in JBoss AS/EAP 5)

by Dan Allen (JIRA)

Bind BeanManager to JNDI when naming context is read/write (as in JBoss AS/EAP 5) --------------------------------------------------------------------------------- Key: WELD-731 URL: https://jira.jboss.org/browse/WELD-731 Project: Weld Issue Type: Feature Request Components: Servlet Container Support Affects Versions: 1.1.0.Beta1 Reporter: Dan Allen Fix For: 1.1.0.CR1 It's possible for the Weld servlet listener to be proactive and bind the BeanManager to JNDI when the naming context is read/write, as it is in JBoss AS and EAP 5. There's another good reason why this needs to be done. JBoss AS does not support defining naming resources in context.xml (which on JBoss AS is WEB-INF/context.xml). Therefore, there's no other way to push the BeanManager into JNDI. The logic for this feature is pretty straightforward. Look for the BeanManager in JNDI. If it's not there, attempt to put it there. If that fails, just log a warning message that the BeanManager will not be available in JNDI. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

7
11
0 / 0

[JBoss JIRA] Created: (WELD-413) It is not possible to add identical beans through BeforeBeanDiscovery.addAnnotatedType

by Stuart Douglas (JIRA)

It is not possible to add identical beans through BeforeBeanDiscovery.addAnnotatedType -------------------------------------------------------------------------------------- Key: WELD-413 URL: https://jira.jboss.org/jira/browse/WELD-413 Project: Weld Issue Type: Bug Affects Versions: 1.0.1.CR1 Reporter: Stuart Douglas Priority: Minor Adding a bean that is exactly the same as an existing bean results in the added bean being ignored. I can't think of a use case for having two beans exactly the same, however it still should work, and may be a symptom of a larger problem. -- 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

12 years, 1 month

4
8
0 / 0

[JBoss JIRA] (WELD-999) Interceptor binding transitivity broken

by Jozef Hartinger (Created) (JIRA)

Interceptor binding transitivity broken --------------------------------------- Key: WELD-999 URL: https://issues.jboss.org/browse/WELD-999 Project: Weld Issue Type: Bug Components: Interceptors and Decorators Affects Versions: 1.1.2.Final Reporter: Jozef Hartinger Fix For: 1.2.0.Beta1 See org.jboss.weld.tests.interceptors.binding.transitivity.InterceptorBindingTransitivityTest -- 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, 1 month

7
8
0 / 0

[JBoss JIRA] (WELD-27) Consider using JBoss maven plugin, not ant for example builds

by Jozef Hartinger (JIRA)

[ https://issues.jboss.org/browse/WELD-27?page=com.atlassian.jira.plugin.sy... ] Jozef Hartinger updated WELD-27: -------------------------------- Fix Version/s: 2.0.0.Alpha2 > Consider using JBoss maven plugin, not ant for example builds > ------------------------------------------------------------- > > Key: WELD-27 > URL: https://issues.jboss.org/browse/WELD-27 > Project: Weld > Issue Type: Task > Components: Examples > Reporter: Pete Muir > Assignee: Ales Justin > Fix For: 1.2.0.Beta1, 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

12 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues March 2012