December 2010 - weld-issues - Jboss List Archives

[JBoss JIRA] Created: (WELD-738) Remove javassist dependencies from the proxies

by Stuart Douglas (JIRA)

Remove javassist dependencies from the proxies ---------------------------------------------- Key: WELD-738 URL: https://jira.jboss.org/browse/WELD-738 Project: Weld Issue Type: Feature Request Components: Proxies Affects Versions: 1.1.0.Beta1 Reporter: Stuart Douglas There is no need for the proxies to continue to use javassist interfaces, as the javassist proxy layer is not longer in use. The proxies still rely on javassist.util.proxy.MethodHandler and javassist.util.proxy.ProxyObject Both of these should be replaced with weld specific interfaces. -- 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

14 years, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (WELD-774) When a normal scoped bean method returns 'this' the proxy should detect this and return an instance of the proxy instead

by Stuart Douglas (JIRA)

When a normal scoped bean method returns 'this' the proxy should detect this and return an instance of the proxy instead ------------------------------------------------------------------------------------------------------------------------ Key: WELD-774 URL: https://jira.jboss.org/browse/WELD-774 Project: Weld Issue Type: Feature Request Affects Versions: 1.1.0.Beta2 Reporter: Stuart Douglas Assignee: Stuart Douglas -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
5
0 / 0

[JBoss JIRA] Created: (WELD-479) Detect circular dependencies in @Dependant scoped beans

by Stuart Douglas (JIRA)

Detect circular dependencies in @Dependant scoped beans ------------------------------------------------------- Key: WELD-479 URL: https://jira.jboss.org/jira/browse/WELD-479 Project: Weld Issue Type: Bug Reporter: Stuart Douglas Assignee: Stuart Douglas According to 5.4: "Beans with scope @Dependent never have circular dependencies", we should detect this at deployment time and throw an error. -- 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

14 years, 1 month

2
12
0 / 0

[JBoss JIRA] Created: (WELD-721) The ClassTransformer cache needs to be cleared when adding Qualifiers/InterceptorBindings etc

by Stuart Douglas (JIRA)

The ClassTransformer cache needs to be cleared when adding Qualifiers/InterceptorBindings etc --------------------------------------------------------------------------------------------- Key: WELD-721 URL: https://jira.jboss.org/browse/WELD-721 Project: Weld Issue Type: Bug Reporter: Stuart Douglas When a Qualifier/Scope/InterceptorBinding is added through the SPI we need to clear the ClassTransformer cache, as the cached information may not longer be correct. -- 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

14 years, 1 month

2
6
0 / 0

[JBoss JIRA] Created: (WELD-728) Cannot create proxies for default packaged beans

by Sivakumar Thyagarajan (JIRA)

Cannot create proxies for default packaged beans ------------------------------------------------ Key: WELD-728 URL: https://jira.jboss.org/browse/WELD-728 Project: Weld Issue Type: Bug Components: Proxies Affects Versions: 1.1.0.Beta1 Reporter: Sivakumar Thyagarajan I have a developer test that has a ManagedBean [1] as part of the default package [ie has no package declaration]. When an interceptor binding is applied to this bean (@Tester applied to method foo()), proxy creation fails with an NPE. Caused by: org.jboss.weld.exceptions.DeploymentException at org.jboss.weld.bean.ManagedBean.applyInterceptors(ManagedBean.java:600) at org.jboss.weld.bean.ManagedBean$ManagedBeanInjectionTarget.produce(ManagedBean.java:256) at org.jboss.weld.bean.ManagedBean.create(ManagedBean.java:338) at org.jboss.weld.context.DependentContext.get(DependentContext.java:62) at org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:660) at org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:734) at org.jboss.weld.manager.BeanManagerImpl.getInjectableReference(BeanManagerImpl.java:757) at org.jboss.weld.injection.FieldInjectionPoint.inject(FieldInjectionPoint.java:118) at org.jboss.weld.util.Beans.injectBoundFields(Beans.java:840) at org.jboss.weld.util.Beans.injectFieldsAndInitializers(Beans.java:852) at org.jboss.weld.manager.SimpleInjectionTarget$1.proceed(SimpleInjectionTarget.java:122) at org.glassfish.weld.services.InjectionServicesImpl.aroundInject(InjectionServicesImpl.java:134) at org.jboss.weld.injection.InjectionContextImpl.run(InjectionContextImpl.java:50) at org.jboss.weld.manager.SimpleInjectionTarget.inject(SimpleInjectionTarget.java:116) at org.glassfish.weld.services.JCDIServiceImpl.createManagedObject(JCDIServiceImpl.java:227) at org.glassfish.weld.services.JCDIServiceImpl.createManagedObject(JCDIServiceImpl.java:181) at com.sun.enterprise.container.common.impl.managedbean.ManagedBeanManagerImpl.createManagedBean(ManagedBeanManagerImpl.java:478) at com.sun.enterprise.container.common.impl.managedbean.ManagedBeanManagerImpl.createManagedBean(ManagedBeanManagerImpl.java:428) at com.sun.enterprise.container.common.impl.util.InjectionManagerImpl.createManagedObject(InjectionManagerImpl.java:300) ... 28 more Caused by: java.lang.NullPointerException at org.jboss.weld.bean.proxy.ProxyFactory.getProxyName(ProxyFactory.java:167) at org.jboss.weld.bean.proxy.ProxyFactory.<init>(ProxyFactory.java:104) at org.jboss.weld.bean.ManagedBean.applyInterceptors(ManagedBean.java:594) [1] https://fisheye4.cenqua.com/browse/glassfish-svn/trunk/v2/appserv-tests/d... or https://glassfish-svn.dev.java.net/source/browse/glassfish-svn/trunk/v2/a... -- 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

14 years, 1 month

4
7
0 / 0

[JBoss JIRA] Created: (WELD-737) Proxy instantiation fails with IllegalAccessError for Beans with package private constructor

by Sivakumar Thyagarajan (JIRA)

Proxy instantiation fails with IllegalAccessError for Beans with package private constructor -------------------------------------------------------------------------------------------- Key: WELD-737 URL: https://jira.jboss.org/browse/WELD-737 Project: Weld Issue Type: Bug Components: Proxies Affects Versions: 1.1.0.Beta1 Reporter: Sivakumar Thyagarajan Attachments: package-private-constructor-issue.tar.bz2 For Beans with package private constructors, proxy instantiation fails with an Illegal access error as shown below. Since 1.1.0.Beta1 the proxy creation logic in ProxyFactory.addConstructors handles private constructors correctly but doesn't consider package private constructors. ---- Caused by: java.lang.IllegalAccessError: tried to access method org.glassfish.tests.proxies.TestSessionScopedBean.<init>()V from class org.glassfish.tests.proxies.org$jboss$weld$bean-$export$work$workspaces$gfv3$v3$distributions$glassfish$target$glassfish3$glassfish$domains$domain1$applications$jsr88-1370237334428885039$-ManagedBean-class_org$glassfish$tests$proxies$TestSessionScopedBean_$$_WeldProxy at org.glassfish.tests.proxies.org$jboss$weld$bean-$export$work$workspaces$gfv3$v3$distributions$glassfish$target$glassfish3$glassfish$domains$domain1$applications$jsr88-1370237334428885039$-ManagedBean-class_org$glassfish$tests$proxies$TestSessionScopedBean_$$_WeldProxy.<init>(org$jboss$weld$bean-$export$work$workspaces$gfv3$v3$distributions$glassfish$target$glassfish3$glassfish$domains$domain1$applications$jsr88-1370237334428885039$-ManagedBean-class_org$glassfish$tests$proxies$TestSessionScopedBean_$$_WeldProxy.java) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at java.lang.Class.newInstance0(Class.java:355) at java.lang.Class.newInstance(Class.java:308) at org.jboss.weld.util.reflection.SecureReflections$16.work(SecureReflections.java:396) at org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:54) at org.jboss.weld.util.reflection.SecureReflectionAccess.runAsInstantiation(SecureReflectionAccess.java:216) at org.jboss.weld.util.reflection.SecureReflections.newInstance(SecureReflections.java:391) at org.jboss.weld.bean.proxy.ProxyFactory.create(ProxyFactory.java:218) at org.jboss.weld.bean.proxy.ClientProxyProvider.createClientProxy(ClientProxyProvider.java:89) at org.jboss.weld.bean.proxy.ClientProxyProvider.access$000(ClientProxyProvider.java:40) at org.jboss.weld.bean.proxy.ClientProxyProvider$1.apply(ClientProxyProvider.java:53) at org.jboss.weld.bean.proxy.ClientProxyProvider$1.apply(ClientProxyProvider.java:44) at com.google.common.collect.ComputingConcurrentHashMap.compute(ComputingConcurrentHashMap.java:206) ---- -- 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

14 years, 1 month

3
16
0 / 0

[JBoss JIRA] Created: (WELD-713) Support PostConstruct callbacks in Extension class

by Sivakumar Thyagarajan (JIRA)

Support PostConstruct callbacks in Extension class -------------------------------------------------- Key: WELD-713 URL: https://jira.jboss.org/browse/WELD-713 Project: Weld Issue Type: Feature Request Components: Bootstrap and Metamodel API Reporter: Sivakumar Thyagarajan As indicated in the scenario in WELD-712, it is sometimes useful to get to know after a portable extension class has been instantiated, so that the state of the Extension could be initialized [ie not establishing state in the constructor and having it called twice when the Extension is proxied]. Though the specification does not require this, it would be useful to support @PostConstruct callback on Extension class. -- 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

14 years, 1 month

2
3
0 / 0

[JBoss JIRA] Created: (WELD-755) conversation.end() followed by conversation.begin() changes cid

by Clint Popetz (JIRA)

conversation.end() followed by conversation.begin() changes cid --------------------------------------------------------------- Key: WELD-755 URL: https://jira.jboss.org/browse/WELD-755 Project: Weld Issue Type: Bug Reporter: Clint Popetz Currently ConversationImpl.end() sets the cid to null. If you then begin() another conversation in the same request, you'll get a new cid, but AbstractConversationImpl will not flush the conversation to the session under than new cid, so if you propagated that new cid to the next request and try to load the conversation, it will not find it. ConversationImpl.end() should probably save away the cid that it had, and re-use it if begin() is called again. -- 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

14 years, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (WELD-364) Remote EJB methods should be able to observe

by Nicklas Karlsson (JIRA)

Remote EJB methods should be able to observe -------------------------------------------- Key: WELD-364 URL: https://jira.jboss.org/jira/browse/WELD-364 Project: Weld Issue Type: Bug Affects Versions: 1.0.0.GA Reporter: Nicklas Karlsson Fix For: 1.0.1.CR1 Unneccessary restriction is currently present -- 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

14 years, 1 month

3
9
0 / 0

[JBoss JIRA] Created: (WELD-746) Observer inheritance should take into consideration EJB semantics

by Marius Bogoevici (JIRA)

Observer inheritance should take into consideration EJB semantics ----------------------------------------------------------------- Key: WELD-746 URL: https://jira.jboss.org/browse/WELD-746 Project: Weld Issue Type: Bug Affects Versions: 1.1.0.Beta2 Reporter: Marius Bogoevici Assignee: Pete Muir Fix For: 1.1.0.Beta3 This is illustrated in org.jboss.jsr299.tck.tests.event.observer.enterprise.EnterpriseEventInheritanceTest as of 1.0.2.CR3. In the affected version of Weld, IndirectStockWatcher and LazyFarmer are expected to observe events. However, those classes are session beans, and the observer methods are not part of their business interface as defined by the EJB 3.1 spec (4.9.2.1 Session Bean superclasses: "the client views exposed by a particular session bean are not inherited by a subclass that also happens to define a session bean"). This currently fails in JBoss AS trunk b/c of a proxy issue (in later revisions, the EjbDescriptor does not return the inherited interfaces as business interfaces, and the methods are not found on the session bean proxy). -- 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

14 years, 1 month

2
4
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues December 2010