April 2010 - weld-issues - Jboss List Archives

[JBoss JIRA] Created: (WELD-500) beans.xsd doesn't allow other elements to be nested

by Pete Muir (JIRA)

beans.xsd doesn't allow other elements to be nested --------------------------------------------------- Key: WELD-500 URL: https://jira.jboss.org/jira/browse/WELD-500 Project: Weld Issue Type: Bug Components: CDI API Reporter: Pete Muir -- 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
3
0 / 0

[JBoss JIRA] Created: (WELD-328) Do nightly build of distribution

by Pete Muir (JIRA)

Do nightly build of distribution -------------------------------- Key: WELD-328 URL: https://jira.jboss.org/jira/browse/WELD-328 Project: Weld Issue Type: Task Components: Infrastructure Reporter: Pete Muir Fix For: 1.0.1.CR1 -- 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
5
0 / 0

[JBoss JIRA] Created: (WELD-483) Client proxies are using the wrong CreationalContexts sometimes

by David Allen (JIRA)

Client proxies are using the wrong CreationalContexts sometimes --------------------------------------------------------------- Key: WELD-483 URL: https://jira.jboss.org/jira/browse/WELD-483 Project: Weld Issue Type: Bug Reporter: David Allen Fix For: 1.0.2.CR1 There are cases where the ThreadLocal which keeps a WeldCreationalContext already has a CC from some prior execution of the code. In other words, these appear to be leaking somehow across bean creations. This can cause problems with test suites by reusing beans from a different test. -- 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

2
4
0 / 0

[JBoss JIRA] Created: (WELD-453) Disable use of Javassist ProxyFactory cache due to leaks

by David Allen (JIRA)

Disable use of Javassist ProxyFactory cache due to leaks -------------------------------------------------------- Key: WELD-453 URL: https://jira.jboss.org/jira/browse/WELD-453 Project: Weld Issue Type: Bug Affects Versions: 1.0.1.Final Reporter: David Allen Assignee: David Allen Fix For: 1.0.2.CR1 The ProxyFactory proxy class cache is a broken concept that cannot work in Java unless a global AS service is established and all proxies are created through the service. But that would degrade performance as well. Since Weld stores the proxy class created for each bean and decorator already, this cache is not actually used. To eliminate the classloader leaks and the heap memory leaks from this cache, it should be disabled every time before a new proxy class is created. -- 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

2
2
0 / 0

[JBoss JIRA] Created: (WELD-463) Unable to inject MessageDrivenContext into a Message Driven Bean

by Ian (JIRA)

Unable to inject MessageDrivenContext into a Message Driven Bean ---------------------------------------------------------------- Key: WELD-463 URL: https://jira.jboss.org/jira/browse/WELD-463 Project: Weld Issue Type: Bug Affects Versions: 1.0.1.Final Environment: JBoss 6.0.0 M2 with Weld 1.0.1 Final, Windows XP SP3 Reporter: Ian When I try to inject a MessageDrivenContext into a Message Driven Bean, I get errors as the bean is created. The code for the Message Driven Bean is: MessageDriven(activationConfig = { @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"), @ActivationConfigProperty(propertyName = "destination", propertyValue = "/queue/NotificationsQueue")}) public class OptinNotificationProcessor implements MessageListener { @Resource private MessageDrivenContext context; @Inject private Logger logger; public void onMessage(Message message) { etc etc } The problem occurs when I use the @Resource tag with the MessageDrivenContext. If I take that out, the code sort of works. But if I put it in, I get the stacktrace shown at the bottom. As an aside, the logger injection works if I remove the @Resource tag so I know injection is working. The stacktrace is as follows: 10:05:18,673 ERROR [org.jboss.aspects.tx.TxPolicy] javax.ejb.EJBTransactionRolledbackException: java.lang.reflect.InvocationTargetException 10:05:18,673 ERROR [org.jboss.resource.adapter.jms.inflow.JmsServerSession] Unexpected error delivering message delegator->JBossMessage[5192369433149442]:PERSISTENT, deliveryId=0: javax.ejb.EJBTransactionRolledbackException: java.lang.reflect.InvocationTargetException at org.jboss.ejb3.tx.Ejb3TxPolicy.handleInCallerTx(Ejb3TxPolicy.java:115) at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:130) at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:194) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.ejb3.tx.NullInterceptor.invoke(NullInterceptor.java:42) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.ejb3.security.Ejb3AuthenticationInterceptorv2.invoke(Ejb3AuthenticationInterceptorv2.java:80) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.ejb3.BlockContainerShutdownInterceptor.invoke(BlockContainerShutdownInterceptor.java:67) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aspects.currentinvocation.CurrentInvocationInterceptor.invoke(CurrentInvocationInterceptor.java:67) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.ejb3.interceptor.EJB3TCCLInterceptor.invoke(EJB3TCCLInterceptor.java:86) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.ejb3.mdb.MessagingContainer.localInvoke(MessagingContainer.java:282) at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.delivery(MessageInflowLocalProxy.java:299) at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:152) at $Proxy281.onMessage(Unknown Source) at org.jboss.resource.adapter.jms.inflow.JmsServerSession.onMessage(JmsServerSession.java:179) at org.jboss.jms.client.container.ClientConsumer.callOnMessageStatic(ClientConsumer.java:160) at org.jboss.jms.client.container.SessionAspect.handleRun(SessionAspect.java:831) at org.jboss.aop.advice.org.jboss.jms.client.container.SessionAspect_z_handleRun_6405193.invoke(SessionAspect_z_handleRun_6405193.java) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170) at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:86) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.jms.client.delegate.ClientSessionDelegate.run(ClientSessionDelegate.java) at org.jboss.jms.client.JBossSession.run(JBossSession.java:199) at org.jboss.resource.adapter.jms.inflow.JmsServerSession.run(JmsServerSession.java:236) at org.jboss.resource.work.WorkWrapper.run(WorkWrapper.java:172) at org.jboss.threads.SimpleDirectExecutor.execute(SimpleDirectExecutor.java:33) at org.jboss.threads.QueueExecutor.runTask(QueueExecutor.java:780) at org.jboss.threads.QueueExecutor.access$100(QueueExecutor.java:45) at org.jboss.threads.QueueExecutor$Worker.run(QueueExecutor.java:800) at java.lang.Thread.run(Thread.java:619) at org.jboss.threads.JBossThread.run(JBossThread.java:122) Caused by: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException at org.jboss.ejb3.interceptors.container.AbstractContainer.invokeCallback(AbstractContainer.java:262) at org.jboss.ejb3.EJBContainer.invokeCallback(EJBContainer.java:1161) at org.jboss.ejb3.EJBContainer.invokePostConstruct(EJBContainer.java:1170) at org.jboss.ejb3.EJBContainer.invokePostConstruct(EJBContainer.java:1181) at org.jboss.ejb3.pool.AbstractPool.create(AbstractPool.java:93) at org.jboss.ejb3.pool.AbstractPool.create(AbstractPool.java:73) at org.jboss.ejb3.pool.StrictMaxPool.get(StrictMaxPool.java:146) at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:58) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:126) ... 34 more Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.ejb3.interceptors.aop.LifecycleCallbackInterceptorMethodLazyInterceptor.invoke(LifecycleCallbackInterceptorMethodLazyInterceptor.java:109) at org.jboss.aop.joinpoint.ConstructionInvocation.invokeNext(ConstructionInvocation.java:79) at org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor.setup(InvocationContextInterceptor.java:88) at org.jboss.aop.advice.org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor_z_setup_6405193.invoke(InvocationContextInterceptor_z_setup_6405193.java) at org.jboss.aop.joinpoint.ConstructionInvocation.invokeNext(ConstructionInvocation.java:79) at org.jboss.aspects.currentinvocation.CurrentInvocationInterceptor.invoke(CurrentInvocationInterceptor.java:67) at org.jboss.aop.joinpoint.ConstructionInvocation.invokeNext(ConstructionInvocation.java:79) at org.jboss.ejb3.interceptors.container.AbstractContainer.invokeCallback(AbstractContainer.java:258) ... 43 more Caused by: java.lang.RuntimeException: Error looking up java:comp/env/package.optin.notifier.OptinNotificationProcessor/context in JNDI at org.jboss.weld.injection.spi.helpers.AbstractResourceServices.resolveResource(AbstractResourceServices.java:51) at org.jboss.weld.util.Beans.injectEEFields(Beans.java:755) at org.jboss.weld.manager.SimpleInjectionTarget$1.proceed(SimpleInjectionTarget.java:121) at org.jboss.weld.injection.InjectionContextImpl.run(InjectionContextImpl.java:51) at org.jboss.weld.manager.SimpleInjectionTarget.inject(SimpleInjectionTarget.java:116) at org.jboss.weld.integration.ejb.SessionBeanInterceptor.postConstruct(SessionBeanInterceptor.java:97) ... 55 more Caused by: javax.naming.NamingException: Could not dereference object [Root exception is javax.naming.NamingException: Could not dereference object [Root exception is java.lang.NullPointerException]] at org.jnp.interfaces.NamingContext.resolveLink(NamingContext.java:1356) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:819) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:835) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:688) at javax.naming.InitialContext.lookup(InitialContext.java:392) at org.jboss.weld.injection.spi.helpers.AbstractResourceServices.resolveResource(AbstractResourceServices.java:47) ... 60 more Caused by: javax.naming.NamingException: Could not dereference object [Root exception is java.lang.NullPointerException] at org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.java:1508) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:824) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:835) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:688) at javax.naming.InitialContext.lookup(InitialContext.java:392) at org.jnp.interfaces.NamingContext.resolveLink(NamingContext.java:1350) ... 65 more Caused by: java.lang.NullPointerException at org.jboss.ejb3.EJBContextFactory.getObjectInstance(EJBContextFactory.java:57) at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:304) at org.jnp.interfaces.NamingContext.getObjectInstance(NamingContext.java:1483) at org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.java:1500) ... 70 more -- 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

3
3
0 / 0

[JBoss JIRA] Created: (WELD-482) CreationalContext not passed through all phases of bean creation

by David Allen (JIRA)

CreationalContext not passed through all phases of bean creation ---------------------------------------------------------------- Key: WELD-482 URL: https://jira.jboss.org/jira/browse/WELD-482 Project: Weld Issue Type: Bug Components: Scopes & Contexts Reporter: David Allen Assignee: David Allen Fix For: 1.0.2.CR1 The CreationalContext is not passed through to the creation of nested bean instances in all circumstances. This is causing incomplete bean instances to be re-created many times when there is a circular reference chain from an injected bean instance back to one of the beans already being created. -- 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

2
3
0 / 0

[JBoss JIRA] Created: (WELD-506) Private container-invoked methods not working on proxies

by David Allen (JIRA)

Private container-invoked methods not working on proxies -------------------------------------------------------- Key: WELD-506 URL: https://jira.jboss.org/jira/browse/WELD-506 Project: Weld Issue Type: Bug Components: Infrastructure Reporter: David Allen Assignee: David Allen Fix For: 1.0.2.CR1 The proxies do not override any of the private methods, so any which are annotated for events are actually invoked on the proxy object itself rather than the object being proxied. -- 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

2
7
0 / 0

[JBoss JIRA] Created: (WELD-504) Lifecycle event exception logging lacks info

by David Allen (JIRA)

Lifecycle event exception logging lacks info -------------------------------------------- Key: WELD-504 URL: https://jira.jboss.org/jira/browse/WELD-504 Project: Weld Issue Type: Bug Affects Versions: 1.0.1.Final Reporter: David Allen Assignee: David Allen Priority: Blocker Fix For: 1.0.2.CR1 The logging of exceptions accumulated during lifecycle events is only listing the exception messages. The stack traces are also needed along with original causes. -- 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

2
2
0 / 0

[JBoss JIRA] Created: (WELD-509) weld-parent POM should specify maven standard directory for docbook folder

by Lincoln Baxter III (JIRA)

weld-parent POM should specify maven standard directory for docbook folder -------------------------------------------------------------------------- Key: WELD-509 URL: https://jira.jboss.org/jira/browse/WELD-509 Project: Weld Issue Type: Task Components: Infrastructure Reporter: Lincoln Baxter III To follow the Maven way, we want to put the docbook source in src/main/docbook. However, Weld is configured to put the sources right at the root. current Weld way: docs/reference/en-US/*.xml the way it should be: docs/reference/src/main/docbook/en-US/*.xml The <sourceDirectory> element needs to be added: <plugin> <groupId>org.jboss.maven.plugins</groupId> <artifactId>maven-jdocbook-plugin</artifactId> ... <configuration> <sourceDirectory>${project.basedir}/src/main/docbook</sourceDirectory> <sourceDocumentName>master.xml</sourceDocumentName> <masterTranslation>en-US</masterTranslation> ... </configuration> ... </plugin> -- 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
2
0 / 0

[JBoss JIRA] Created: (WELD-495) readme.txt needs to be updated

by asookazian (JIRA)

readme.txt needs to be updated ------------------------------ Key: WELD-495 URL: https://jira.jboss.org/jira/browse/WELD-495 Project: Weld Issue Type: Bug Components: Documentation Affects Versions: 1.0.1.Final Environment: Windows XP, Weld 1.0.1-final, Maven 2.2.1, JBoss AS 6.0.0.M2 Reporter: asookazian Priority: Trivial The readme.txt for weld-1.0.1-final states "Currently, you must use JBoss AS 5.2.0.Beta1 (use nightly builds until released) or above deploy the provided examples out of the box." The current recommended version of JBoss AS is 6.0.0.M2. Also "Other application servers may be supported by the examples in the 1.0.0 release" needs to be fixed as well as this readme.txt is for 1.0.1-final. So perhaps the app servers need to be stated now. -- 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
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues April 2010