May 2012 - weld-issues - Jboss List Archives

[JBoss JIRA] (WELD-1134) NPE on org.jboss.weld.util.reflection.HierarchyDiscovery

by George Gastaldi (JIRA)

George Gastaldi created WELD-1134: ------------------------------------- Summary: NPE on org.jboss.weld.util.reflection.HierarchyDiscovery Key: WELD-1134 URL: https://issues.jboss.org/browse/WELD-1134 Project: Weld Issue Type: Bug Reporter: George Gastaldi I upgraded Forge to Weld 1.1.8.Final, from 1.1.2.Final and now I am getting the following error: {code} com.google.common.collect.ComputationException: java.lang.NullPointerException at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:397) at org.jboss.weld.resources.SharedObjectCache.getTypeClosure(SharedObjectCache.java:82) at org.jboss.weld.resources.SharedObjectFacade.getTypeClosure(SharedObjectFacade.java:65) at org.jboss.weld.introspector.TypeClosureLazyValueHolder.computeValue(TypeClosureLazyValueHolder.java:52) at org.jboss.weld.introspector.TypeClosureLazyValueHolder.computeValue(TypeClosureLazyValueHolder.java:31) at org.jboss.weld.util.LazyValueHolder.get(LazyValueHolder.java:34) at org.jboss.weld.introspector.jlr.AbstractWeldAnnotated.getTypeClosure(AbstractWeldAnnotated.java:193) at org.jboss.weld.introspector.jlr.WeldMethodImpl.of(WeldMethodImpl.java:74) at org.jboss.weld.introspector.jlr.WeldClassImpl.<init>(WeldClassImpl.java:261) at org.jboss.weld.introspector.jlr.WeldClassImpl.of(WeldClassImpl.java:115) at org.jboss.weld.resources.ClassTransformer$TransformAnnotatedTypeToWeldClass.apply(ClassTransformer.java:88) at org.jboss.weld.resources.ClassTransformer$TransformAnnotatedTypeToWeldClass.apply(ClassTransformer.java:78) at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) at org.jboss.weld.resources.ClassTransformer.loadClass(ClassTransformer.java:190) at org.jboss.weld.bootstrap.BeanDeployer.addClass(BeanDeployer.java:86) at org.jboss.weld.bootstrap.BeanDeployer.addClasses(BeanDeployer.java:123) at org.jboss.weld.bootstrap.BeanDeployment.createBeans(BeanDeployment.java:184) at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:350) at org.jboss.weld.bootstrap.api.helpers.ForwardingBootstrap.deployBeans(ForwardingBootstrap.java:70) at org.jboss.weld.environment.se.Weld.initialize(Weld.java:133) at org.jboss.forge.shell.Bootstrap$1.run(Bootstrap.java:132) at java.lang.Thread.run(Thread.java:722) Caused by: java.lang.NullPointerException at java.lang.reflect.Array.newArray(Native Method) at java.lang.reflect.Array.newInstance(Array.java:70) at org.jboss.weld.util.reflection.HierarchyDiscovery.discoverTypes(HierarchyDiscovery.java:99) at org.jboss.weld.util.reflection.HierarchyDiscovery.init(HierarchyDiscovery.java:74) at org.jboss.weld.util.reflection.HierarchyDiscovery.getTypeClosure(HierarchyDiscovery.java:58) at org.jboss.weld.resources.SharedObjectCache$4.apply(SharedObjectCache.java:58) at org.jboss.weld.resources.SharedObjectCache$4.apply(SharedObjectCache.java:55) at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) {code} This line is the causing issue: Class<?> arrayClass = Array.newInstance(Reflections.getRawType(genericComponentType), 0).getClass(); genericComponentType is sun.reflect.generics.reflectiveObjects.TypeVariableImpl. Need a test case to simulate that -- 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, 11 months

3
4
0 / 0

[JBoss JIRA] (WELD-987) Misleading definition error for decorator with observer method

by Martin Kouba (Created) (JIRA)

Misleading definition error for decorator with observer method -------------------------------------------------------------- Key: WELD-987 URL: https://issues.jboss.org/browse/WELD-987 Project: Weld Issue Type: Bug Affects Versions: 1.1.2.Final Environment: JBoss AS7 Reporter: Martin Kouba Priority: Minor CDI 1.0 section 10.4.2 states: "Interceptors and decorators may not declare observer methods. If an interceptor or decorator has a method with a paramet- er annotated @Observes, the container automatically detects the problem and treats it as a definition error." Following definition error is detected for decorator with observer method: *WELD-001419 - DECORATOR_CLASS_NOT_BEAN_CLASS_OF_DECORATOR* New definition error like *DECORATORS_CANNOT_HAVE_OBSERVER_METHODS* would be more appropriate. TCK test for this scenario (CDI 1.1 master branch): 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, 11 months

6
6
0 / 0

[JBoss JIRA] (WELD-1119) ContainerLifecycleEventPreloader fails to start on a single core machine

by Jozef Hartinger (JIRA)

Jozef Hartinger created WELD-1119: ------------------------------------- Summary: ContainerLifecycleEventPreloader fails to start on a single core machine Key: WELD-1119 URL: https://issues.jboss.org/browse/WELD-1119 Project: Weld Issue Type: Bug Affects Versions: 2.0.0.Alpha2 Reporter: Jozef Hartinger Assignee: Jozef Hartinger Priority: Critical Fix For: 2.0.0.Alpha3 -- 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, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (WELD-920) Memory leak through the creational context of an @AppScoped bean when injecting Instance<>

by Adam Warski (JIRA)

Memory leak through the creational context of an @AppScoped bean when injecting Instance<> ------------------------------------------------------------------------------------------ Key: WELD-920 URL: https://issues.jboss.org/browse/WELD-920 Project: Weld Issue Type: Bug Components: Scopes & Contexts Affects Versions: 1.1.1.Final, 1.1.0.CR3 Reporter: Adam Warski Given a simple dependent-scoped bean: public class InstanceBean {}, and an application-scoped bean (see below) to which an instance of the dependent-scoped bean is injected, each time the get() method is called on the instance, even though it's not used, a reference to it stays in the creational context of the application scoped bean (http://screencast.com/t/XqjQ1GB7Wv3). That way after several requests, where each one calls the method, more and more memory is leaked (http://screencast.com/t/s1VBx49i). Attached is a simple web application demonstrating this. To reproduce, deploy to AS6, click the "leak" button several times, and analyze the heap dump e.g. in JProfiler. @ApplicationScoped @Named("test") public class AppScopedBean { private Instance<InstanceBean> instanceBeanInstance; @Inject public AppScopedBean(Instance<InstanceBean> instanceBeanInstance) { this.instanceBeanInstance = instanceBeanInstance; } public AppScopedBean() { } public void leakOneInstance() { System.out.println("Leaked!"); instanceBeanInstance.get(); } } -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

5
17
0 / 0

[JBoss JIRA] (WELD-1024) Missing check that specializing bean has all the bean types of specialized bean

by Martin Kouba (Created) (JIRA)

Missing check that specializing bean has all the bean types of specialized bean ------------------------------------------------------------------------------- Key: WELD-1024 URL: https://issues.jboss.org/browse/WELD-1024 Project: Weld Issue Type: Bug Reporter: Martin Kouba Spec *4.3.1. Direct and indirect specialization* states: "Furthermore, X must have all the bean types of Y. If X does not have some bean type of Y, the container automatically detects the problem and treats it as a definition error." However definition error is not detected and application is deployed in corrupted state. -- 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, 11 months

4
3
0 / 0

[JBoss JIRA] (WELD-1100) Add annotation provider SPI

by Stuart Douglas (JIRA)

Stuart Douglas created WELD-1100: ------------------------------------ Summary: Add annotation provider SPI Key: WELD-1100 URL: https://issues.jboss.org/browse/WELD-1100 Project: Weld Issue Type: Feature Request Reporter: Stuart Douglas JDK annotation based reflection is slow, it would be good if we could leverage Jandex to use AS7 existing jandex annotation indexes. -- 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, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (WELD-510) Support for Portlet 2.0

by Neil Griffin (JIRA)

Support for Portlet 2.0 ----------------------- Key: WELD-510 URL: https://jira.jboss.org/jira/browse/WELD-510 Project: Weld Issue Type: Feature Request Affects Versions: 1.0.1.Final Reporter: Neil Griffin There are some folks trying to use the PortletFaces Bridge for JSF 2.0 + Portlet 2.0 in Glassfish V3, but Weld is causing an issue. Original Post: http://www.portletfaces.org/community/forums/-/message_boards/message/430... Here is a simple stacktrace of the problem: Caused by: java.lang.IllegalStateException: Weld doesn not support using JSF in an non-servlet environment at org.jboss.weld.jsf.JsfHelper.getModuleBeanManager(JsfHelper.java:119) at org.jboss.weld.jsf.WeldPhaseListener.initiateSessionAndConversation(WeldPhaseListener The code for the bridge API is here: http://svn.portletfaces.org/svn/portletfaces/bridge/org.portletfaces.brid... The code for the bridge IMPL is here: http://svn.portletfaces.org/svn/portletfaces/bridge/org.portletfaces.brid... And the code for a sample portlet is here: http://svn.portletfaces.org/svn/portletfaces/portlets/sample/jsf-2.0-job-... -- 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, 11 months

12
36
0 / 0

[JBoss JIRA] (WELD-1130) Weld does not call setAttribute for modified conversation and session scoped beans

by Stuart Douglas (JIRA)

Stuart Douglas created WELD-1130: ------------------------------------ Summary: Weld does not call setAttribute for modified conversation and session scoped beans Key: WELD-1130 URL: https://issues.jboss.org/browse/WELD-1130 Project: Weld Issue Type: Bug Components: Clustering Affects Versions: 2.0.0.Alpha2, 1.1.8.Final Reporter: Stuart Douglas This means that in some containers/configurations replication of CDI beans will not happen. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (WELD-1124) ResourceProducer from Weld 1.1 testsuite won't compile on JDK 7

by Ron Šmeral (JIRA)

Ron Šmeral created WELD-1124: -------------------------------- Summary: ResourceProducer from Weld 1.1 testsuite won't compile on JDK 7 Key: WELD-1124 URL: https://issues.jboss.org/browse/WELD-1124 Project: Weld Issue Type: Bug Environment: JDK 7, Weld 1.2.0-SNAPSHOT testsuite Reporter: Ron Šmeral The testsuite doesn't compile on any JDK 7, tested on Oracle, IBM and OpenJDK. The problem seems to be in the class org.jboss.weld.tests.resources.ws.ResourceProducer. According to the documentation of {{value}} field of {{WebServiceRef}}, it should reference ??"the service class, *always a type extending javax.xml.ws.Service*"??, which is not true for the class {{TranslatorService}} referenced by {{WebServiceRef}} in {{ResourceProducer}}. The compilation fails with: {noformat} .../dev/weld/weld/tests-arquillian/src/test/java/org/jboss/weld/tests/resources/ws/ResourceProducer.java:[26,39] error: incompatible types {noformat} After changing the {{TranslatorService}} to extend {{Service}}, the class compiles and the test ({{testWebServiceResourceDeclaration}}) passes. -- 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, 11 months

2
2
0 / 0

[JBoss JIRA] (WELD-1116) Weld 2 does not build on JDK7

by Jozef Hartinger (JIRA)

Jozef Hartinger created WELD-1116: ------------------------------------- Summary: Weld 2 does not build on JDK7 Key: WELD-1116 URL: https://issues.jboss.org/browse/WELD-1116 Project: Weld Issue Type: Bug Affects Versions: 2.0.0.Alpha2 Reporter: Jozef Hartinger Assignee: Jozef Hartinger Fix For: 2.0.0.Alpha3 [ERROR] COMPILATION ERROR : [INFO] ------------------------------------------------------------- [ERROR] /qa/hudson_ws/workspace/Weld-2.x-CI-JDK7/weld/tests-arquillian/src/test/java/org/jboss/weld/tests/resources/ws/ResourceProducer.java:[26,39] error: incompatible types -- 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, 11 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues May 2012