August 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Moved: (JBAS-8301) WeldListener should be the first Servlet Listener to fire

by Pete Muir (JIRA)

[ https://jira.jboss.org/browse/JBAS-8301?page=com.atlassian.jira.plugin.sy... ] Pete Muir moved WELDINT-56 to JBAS-8301: ---------------------------------------- Project: JBoss Application Server (was: Weld Integration) Key: JBAS-8301 (was: WELDINT-56) Component/s: Weld/CDI (was: JBoss Services (Other)) > WeldListener should be the first Servlet Listener to fire > --------------------------------------------------------- > > Key: JBAS-8301 > URL: https://jira.jboss.org/browse/JBAS-8301 > Project: JBoss Application Server > Issue Type: Bug > Components: Weld/CDI > Reporter: Nicklas Karlsson > Priority: Critical > > The WeldListener should be the first ServletListener to fire since if it's not, the CDI contexts etc. are not available for any application ServletListener that might want to use these features -- 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

15 years, 11 months

1
0
0 / 0

[JBoss JIRA] Moved: (JBAS-8303) Investigate better ways of doing injection into into EJB instances than using an interceptor

by Pete Muir (JIRA)

[ https://jira.jboss.org/browse/JBAS-8303?page=com.atlassian.jira.plugin.sy... ] Pete Muir moved WELDINT-9 to JBAS-8303: --------------------------------------- Project: JBoss Application Server (was: Weld Integration) Key: JBAS-8303 (was: WELDINT-9) Component/s: Weld/CDI (was: JBoss EJB 3.0 integration) Fix Version/s: 6.0.0.CR1 (was: 6.0.0.CR1) > Investigate better ways of doing injection into into EJB instances than using an interceptor > -------------------------------------------------------------------------------------------- > > Key: JBAS-8303 > URL: https://jira.jboss.org/browse/JBAS-8303 > Project: JBoss Application Server > Issue Type: Feature Request > Components: Weld/CDI > Reporter: Pete Muir > Fix For: 6.0.0.CR1 > > > Especially, a better way of getting the EJB name -- 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

15 years, 11 months

1
0
0 / 0

[JBoss JIRA] Moved: (JBAS-8302) Message Driven Beans fail to run if an item is on the queue before the application server is started up

by Pete Muir (JIRA)

[ https://jira.jboss.org/browse/JBAS-8302?page=com.atlassian.jira.plugin.sy... ] Pete Muir moved WELDINT-61 to JBAS-8302: ---------------------------------------- Project: JBoss Application Server (was: Weld Integration) Key: JBAS-8302 (was: WELDINT-61) Component/s: Weld/CDI (was: Weld Bootstrapper) Fix Version/s: 6.0.0.CR1 (was: 6.0.0.CR1) > Message Driven Beans fail to run if an item is on the queue before the application server is started up > ------------------------------------------------------------------------------------------------------- > > Key: JBAS-8302 > URL: https://jira.jboss.org/browse/JBAS-8302 > Project: JBoss Application Server > Issue Type: Bug > Components: Weld/CDI > Environment: JBoss 6.0.0-M3 with Weld 1.0.1-Final > Reporter: Ian > Assignee: Marius Bogoevici > Fix For: 6.0.0.CR1 > > > The scenario occurs when I start up an application with an MDB and there is a message on the queue before the application starts. If a message appears on the queue after application startup, there are no issues and everything processes correctly. During application startup, I get "StackTrace #1" - the error is to do with being unable to locate the BeanManager. After the application starts up, I continually get "StackTrace #2" - which means no further messages ever get delivered to the MDB. > StackTrace #1 > 11:08:53,949 ERROR [org.jboss.aspects.tx.TxPolicy] javax.ejb.EJBTransactionRolledbackException: Unable to inject jndi dependency: env/org.jboss.weld.integration.ejb.SessionBeanInterceptor/beanManager into property org.jboss.weld.integration.ejb.SessionBeanInterceptor.beanManager: WELD-001300 Unable to locate BeanManager > 11:08:53,949 ERROR [org.hornetq.ra.inflow.HornetQMessageHandler] Failed to deliver message: javax.ejb.EJBTransactionRolledbackException: Unable to inject jndi dependency: env/org.jboss.weld.integration.ejb.SessionBeanInterceptor/beanManager into property org.jboss.weld.integration.ejb.SessionBeanInterceptor.beanManager: WELD-001300 Unable to locate BeanManager > at org.jboss.ejb3.tx.Ejb3TxPolicy.handleInCallerTx(Ejb3TxPolicy.java:115) [:1.0.2] > at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:130) [:1.0.0.GA] > at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:194) [:1.0.0.GA] > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) [jboss-aop.jar:2.2.0.Final] > at org.jboss.ejb3.tx.NullInterceptor.invoke(NullInterceptor.java:42) [:1.0.2] > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) [jboss-aop.jar:2.2.0.Final] > at org.jboss.ejb3.security.Ejb3AuthenticationInterceptorv2.invoke(Ejb3AuthenticationInterceptorv2.java:80) [:1.3.1] > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) [jboss-aop.jar:2.2.0.Final] > at org.jboss.ejb3.BlockContainerShutdownInterceptor.invoke(BlockContainerShutdownInterceptor.java:67) [:1.3.1] > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) [jboss-aop.jar:2.2.0.Final] > at org.jboss.ejb3.core.context.CurrentInvocationContextInterceptor.invoke(CurrentInvocationContextInterceptor.java:47) [:1.3.1] > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) [jboss-aop.jar:2.2.0.Final] > at org.jboss.aspects.currentinvocation.CurrentInvocationInterceptor.invoke(CurrentInvocationInterceptor.java:67) [:1.0.1] > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) [jboss-aop.jar:2.2.0.Final] > at org.jboss.ejb3.interceptor.EJB3TCCLInterceptor.invoke(EJB3TCCLInterceptor.java:86) [:1.3.1] > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) [jboss-aop.jar:2.2.0.Final] > at org.jboss.ejb3.mdb.MessagingContainer.localInvoke(MessagingContainer.java:277) [:1.3.1] > at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.delivery(MessageInflowLocalProxy.java:299) [:1.3.1] > at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:152) [:1.3.1] > at $Proxy171.onMessage(Unknown Source) at org.hornetq.ra.inflow.HornetQMessageHandler.onMessage(HornetQMessageHandler.java:259) [:6.0.0.20100429-M3] > at org.hornetq.core.client.impl.ClientConsumerImpl.callOnMessage(ClientConsumerImpl.java:809) [:6.0.0.20100429-M3] > at org.hornetq.core.client.impl.ClientConsumerImpl.access$100(ClientConsumerImpl.java:46) [:6.0.0.20100429-M3] > at org.hornetq.core.client.impl.ClientConsumerImpl$Runner.run(ClientConsumerImpl.java:927) [:6.0.0.20100429-M3] > at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:96) [:6.0.0.20100429-M3] > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_11] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_11] > at java.lang.Thread.run(Thread.java:619) [:1.6.0_11] > Caused by: java.lang.RuntimeException: Unable to inject jndi dependency: env/org.jboss.weld.integration.ejb.SessionBeanInterceptor/beanManager into property org.jboss.weld.integration.ejb.SessionBeanInterceptor.beanManager: WELD-001300 Unable to locate BeanManager > at org.jboss.injection.JndiPropertyInjector.lookup(JndiPropertyInjector.java:82) [:1.3.1] > at org.jboss.injection.JndiPropertyInjector.inject(JndiPropertyInjector.java:99) [:1.3.1] > at org.jboss.injection.JndiPropertyInjector.inject(JndiPropertyInjector.java:89) [:1.3.1] > at org.jboss.ejb3.interceptor.InterceptorInjector.inject(InterceptorInjector.java:49) [:1.3.1] > at org.jboss.ejb3.EJBContainer.createInterceptor(EJBContainer.java:359) [:1.3.1] > at org.jboss.ejb3.BaseContext.initialiseInterceptorInstances(BaseContext.java:112) [:1.3.1] > at org.jboss.ejb3.injection.InjectionHelper.inject(InjectionHelper.java:55) [:1.3.1] > at org.jboss.ejb3.injection.InjectionHelper.inject(InjectionHelper.java:43) [:1.3.1] > at org.jboss.ejb3.mdb.MDBInjectionInvocation.proceed(MDBInjectionInvocation.java:45) [:1.3.1] > at org.jboss.ejb3.injection.InjectionInvocation.invokeTarget(InjectionInvocation.java:97) [:1.3.1] > at org.jboss.ejb3.injection.InjectionInvocation.invokeNext(InjectionInvocation.java:91) [:1.3.1] > at org.jboss.ejb3.core.context.CurrentInvocationContextInterceptor.invoke(CurrentInvocationContextInterceptor.java:47) [:1.3.1] > at org.jboss.ejb3.injection.InjectionInvocation.invokeNext(InjectionInvocation.java:82) [:1.3.1] > at org.jboss.aspects.currentinvocation.CurrentInvocationInterceptor.invoke(CurrentInvocationInterceptor.java:67) [:1.0.1] > at org.jboss.ejb3.injection.InjectionInvocation.invokeNext(InjectionInvocation.java:82) [:1.3.1] > at org.jboss.ejb3.EJBContainer.injectBeanContext(EJBContainer.java:1197) [:1.3.1] > at org.jboss.ejb3.pool.AbstractPool.create(AbstractPool.java:83) [:1.3.1] > at org.jboss.ejb3.pool.AbstractPool.create(AbstractPool.java:73) [:1.3.1] > at org.jboss.ejb3.pool.StrictMaxPool.get(StrictMaxPool.java:146) [:1.3.1] > at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:58) [:1.3.1] > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) [jboss-aop.jar:2.2.0.Final] > at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:126) [:1.0.0.GA] > ... 26 more > Caused by: javax.naming.NamingException: Could not dereference object [Root exception is javax.naming.NamingException: WELD-001300 Unable to locate BeanManager] > at org.jnp.interfaces.NamingContext.resolveLink(NamingContext.java:1356) [:5.0.5.Final] > at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:819) [:5.0.5.Final] > at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:688) [:5.0.5.Final] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_11] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_11] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_11] > at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_11] > at org.jboss.ejb3.EJBContainer$1.invoke(EJBContainer.java:828) [:1.3.1] > at $Proxy163.lookup(Unknown Source) at org.jboss.ejb3.JndiUtil.lookup(JndiUtil.java:44) [:1.3.1] > at org.jboss.injection.JndiPropertyInjector.lookup(JndiPropertyInjector.java:75) [:1.3.1] > ... 47 more > Caused by: javax.naming.NamingException: WELD-001300 Unable to locate BeanManager > at org.jboss.weld.resources.ManagerObjectFactory.getObjectInstance(ManagerObjectFactory.java:50) [:1.0.1.Final] > at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:304) [:1.6.0_11] > at org.jnp.interfaces.NamingContext.getObjectInstance(NamingContext.java:1483) [:5.0.5.Final] > at org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.java:1500) [:5.0.5.Final] > at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:824) [:5.0.5.Final] > at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:835) [:5.0.5.Final] > at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:688) [:5.0.5.Final] > at javax.naming.InitialContext.lookup(InitialContext.java:392) [:1.6.0_11] > at org.jnp.interfaces.NamingContext.resolveLink(NamingContext.java:1350) [:5.0.5.Final] > ... 57 more > StackTrace #2 > 11:09:14,777 ERROR [org.jboss.aspects.tx.TxPolicy] javax.ejb.EJBException: Failed to acquire the pool semaphore, strictTimeout=10000 > 11:09:14,777 ERROR [org.hornetq.ra.inflow.HornetQMessageHandler] Failed to deliver message: javax.ejb.EJBException: Failed to acquire the pool semaphore, strictTimeout=10000 > at org.jboss.ejb3.pool.StrictMaxPool.get(StrictMaxPool.java:127) [:1.3.1] > at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:58) [:1.3.1] > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) [jboss-aop.jar:2.2.0.Final] > at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:126) [:1.0.0.GA] > at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:194) [:1.0.0.GA] > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) [jboss-aop.jar:2.2.0.Final] > at org.jboss.ejb3.tx.NullInterceptor.invoke(NullInterceptor.java:42) [:1.0.2] > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) [jboss-aop.jar:2.2.0.Final] > at org.jboss.ejb3.security.Ejb3AuthenticationInterceptorv2.invoke(Ejb3AuthenticationInterceptorv2.java:80) [:1.3.1] > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) [jboss-aop.jar:2.2.0.Final] > at org.jboss.ejb3.BlockContainerShutdownInterceptor.invoke(BlockContainerShutdownInterceptor.java:67) [:1.3.1] > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) [jboss-aop.jar:2.2.0.Final] > at org.jboss.ejb3.core.context.CurrentInvocationContextInterceptor.invoke(CurrentInvocationContextInterceptor.java:47) [:1.3.1] > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) [jboss-aop.jar:2.2.0.Final] > at org.jboss.aspects.currentinvocation.CurrentInvocationInterceptor.invoke(CurrentInvocationInterceptor.java:67) [:1.0.1] > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) [jboss-aop.jar:2.2.0.Final] > at org.jboss.ejb3.interceptor.EJB3TCCLInterceptor.invoke(EJB3TCCLInterceptor.java:86) [:1.3.1] > at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) [jboss-aop.jar:2.2.0.Final] > at org.jboss.ejb3.mdb.MessagingContainer.localInvoke(MessagingContainer.java:277) [:1.3.1] > at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.delivery(MessageInflowLocalProxy.java:299) [:1.3.1] > at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:152) [:1.3.1] > at $Proxy171.onMessage(Unknown Source) at org.hornetq.ra.inflow.HornetQMessageHandler.onMessage(HornetQMessageHandler.java:259) [:6.0.0.20100429-M3] > at org.hornetq.core.client.impl.ClientConsumerImpl.callOnMessage(ClientConsumerImpl.java:809) [:6.0.0.20100429-M3] > at org.hornetq.core.client.impl.ClientConsumerImpl.access$100(ClientConsumerImpl.java:46) [:6.0.0.20100429-M3] > at org.hornetq.core.client.impl.ClientConsumerImpl$Runner.run(ClientConsumerImpl.java:927) [:6.0.0.20100429-M3] > at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:96) [:6.0.0.20100429-M3] > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_11] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_11] > at java.lang.Thread.run(Thread.java:619) [:1.6.0_11] -- 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

15 years, 11 months

1
0
0 / 0

[JBoss JIRA] Moved: (JBAS-8297) Weld throws error No active contexts for scope type javax.enterprise.context.RequestScoped

by Pete Muir (JIRA)

[ https://jira.jboss.org/browse/JBAS-8297?page=com.atlassian.jira.plugin.sy... ] Pete Muir moved WELDINT-59 to JBAS-8297: ---------------------------------------- Project: JBoss Application Server (was: Weld Integration) Key: JBAS-8297 (was: WELDINT-59) Affects Version/s: (was: 6.0.0.Beta7) Component/s: Weld/CDI (was: Web tier integration) > Weld throws error No active contexts for scope type javax.enterprise.context.RequestScoped > ------------------------------------------------------------------------------------------ > > Key: JBAS-8297 > URL: https://jira.jboss.org/browse/JBAS-8297 > Project: JBoss Application Server > Issue Type: Bug > Components: Weld/CDI > Environment: JBoss 6.0.0.M2, Windows XP SP3 > Reporter: Marcos Antonio > Attachments: solicitacoes.zip > > > 2010-04-22 09:55:36,484 WARN [org.apache.catalina.authenticator.FormAuthenticator] (http-127.0.0.1-8080-1) Unexpected error forwarding to login page: javax.servlet.ServletException: WELD-001303 No active contexts for scope type javax.enterprise.context.RequestScoped -- 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

15 years, 11 months

1
0
0 / 0

[JBoss JIRA] Moved: (JBAS-8294) Weld & Asynchronous servlets on JBoss 6.0 M2

by Pete Muir (JIRA)

[ https://jira.jboss.org/browse/JBAS-8294?page=com.atlassian.jira.plugin.sy... ] Pete Muir moved WELDINT-44 to JBAS-8294: ---------------------------------------- Project: JBoss Application Server (was: Weld Integration) Key: JBAS-8294 (was: WELDINT-44) Component/s: Weld/CDI (was: Web tier integration) Fix Version/s: 6.0.0.CR1 (was: 6.0.0.CR1) > Weld & Asynchronous servlets on JBoss 6.0 M2 > -------------------------------------------- > > Key: JBAS-8294 > URL: https://jira.jboss.org/browse/JBAS-8294 > Project: JBoss Application Server > Issue Type: Bug > Components: Weld/CDI > Reporter: William Draï > Assignee: Pete Muir > Fix For: 6.0.0.CR1 > > > Weld seems to break asynchronous servlets 3 (new in JBossWeb). I think it's because the Weld/JBoss integration maps all requests to the ConversationPropagationFilter that is not marked async-supported . > Strangely this filter is not applied to servlets implementing HttpEventServlet but it's probably a normal JBossWeb behaviour. > Besides that I'm not in a JSF environment so I don't need this conversation propagation, is there any way to disable this filter ? -- 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

15 years, 11 months

1
0
0 / 0

[JBoss JIRA] Moved: (JBAS-8289) Bean class local view not a bean type of a Session bean

by Pete Muir (JIRA)

[ https://jira.jboss.org/browse/JBAS-8289?page=com.atlassian.jira.plugin.sy... ] Pete Muir moved WELDINT-46 to JBAS-8289: ---------------------------------------- Project: JBoss Application Server (was: Weld Integration) Key: JBAS-8289 (was: WELDINT-46) Component/s: Weld/CDI (was: JBoss EJB 3.0 integration) Fix Version/s: 6.0.0.CR1 (was: 6.0.0.CR1) > Bean class local view not a bean type of a Session bean > ------------------------------------------------------- > > Key: JBAS-8289 > URL: https://jira.jboss.org/browse/JBAS-8289 > Project: JBoss Application Server > Issue Type: Bug > Components: Weld/CDI > Reporter: Jozef Hartinger > Fix For: 6.0.0.CR1 > > > org.jboss.jsr299.tck.tests.implementation.enterprise.definition.EnterpriseBeanDefinitionTest.testEnterpriseBeanClassLocalView() > in the TCK trunk -- 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

15 years, 11 months

1
0
0 / 0

[JBoss JIRA] Moved: (JBAS-8290) Implement solid isRemoved() method for SessionObjectReference

by Pete Muir (JIRA)

[ https://jira.jboss.org/browse/JBAS-8290?page=com.atlassian.jira.plugin.sy... ] Pete Muir moved WELDINT-6 to JBAS-8290: --------------------------------------- Project: JBoss Application Server (was: Weld Integration) Key: JBAS-8290 (was: WELDINT-6) Component/s: Weld/CDI (was: JBoss EJB 3.0 integration) Fix Version/s: 6.0.0.CR1 (was: 6.0.0.CR1) > Implement solid isRemoved() method for SessionObjectReference > ------------------------------------------------------------- > > Key: JBAS-8290 > URL: https://jira.jboss.org/browse/JBAS-8290 > Project: JBoss Application Server > Issue Type: Bug > Components: Weld/CDI > Reporter: Pete Muir > Fix For: 6.0.0.CR1 > > > Currently we don't actually detect if the user or EJB container removes the EJB, not WB -- 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

15 years, 11 months

1
0
0 / 0

[JBoss JIRA] Moved: (JBAS-8291) EJB unable to load bean for before transaction completion observer

by Pete Muir (JIRA)

[ https://jira.jboss.org/browse/JBAS-8291?page=com.atlassian.jira.plugin.sy... ] Pete Muir moved WELDINT-38 to JBAS-8291: ---------------------------------------- Project: JBoss Application Server (was: Weld Integration) Key: JBAS-8291 (was: WELDINT-38) Component/s: Weld/CDI (was: JBoss EJB 3.0 integration) Fix Version/s: 6.0.0.CR1 (was: 6.0.0.CR1) > EJB unable to load bean for before transaction completion observer > ------------------------------------------------------------------ > > Key: JBAS-8291 > URL: https://jira.jboss.org/browse/JBAS-8291 > Project: JBoss Application Server > Issue Type: Bug > Components: Weld/CDI > Reporter: Pete Muir > Fix For: 6.0.0.CR1 > > > See org.jboss.jsr299.tck.tests.event.observer.transactional.TransactionalObserversTest.testBeforeTransactionCompletionObserver() -- 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

15 years, 11 months

1
0
0 / 0

[JBoss JIRA] Moved: (JBAS-8292) Weld assumes EJB proxy is always a JDK proxy, it might not be

by Pete Muir (JIRA)

[ https://jira.jboss.org/browse/JBAS-8292?page=com.atlassian.jira.plugin.sy... ] Pete Muir moved WELDINT-45 to JBAS-8292: ---------------------------------------- Project: JBoss Application Server (was: Weld Integration) Key: JBAS-8292 (was: WELDINT-45) Component/s: Weld/CDI (was: JBoss EJB 3.0 integration) Fix Version/s: 6.0.0.CR1 (was: 6.0.0.CR1) > Weld assumes EJB proxy is always a JDK proxy, it might not be > ------------------------------------------------------------- > > Key: JBAS-8292 > URL: https://jira.jboss.org/browse/JBAS-8292 > Project: JBoss Application Server > Issue Type: Bug > Components: Weld/CDI > Reporter: Pete Muir > Assignee: Marius Bogoevici > Fix For: 6.0.0.CR1 > > > Carlo suggests altering the the entire contract to use some EJB3-equivalent for Home objects to allow Weld to create/remove EJB instances. -- 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

15 years, 11 months

1
0
0 / 0

[JBoss JIRA] Moved: (JBAS-8293) JBossSessionObjectReference and JBossSessionBeanDescriptorAdaptor are not serializable due to presence of DeploymentUnit

by Pete Muir (JIRA)

[ https://jira.jboss.org/browse/JBAS-8293?page=com.atlassian.jira.plugin.sy... ] Pete Muir moved WELDINT-34 to JBAS-8293: ---------------------------------------- Project: JBoss Application Server (was: Weld Integration) Key: JBAS-8293 (was: WELDINT-34) Component/s: Weld/CDI (was: JBoss EJB 3.0 integration) Fix Version/s: 6.0.0.CR1 (was: 6.0.0.CR1) > JBossSessionObjectReference and JBossSessionBeanDescriptorAdaptor are not serializable due to presence of DeploymentUnit > ------------------------------------------------------------------------------------------------------------------------ > > Key: JBAS-8293 > URL: https://jira.jboss.org/browse/JBAS-8293 > Project: JBoss Application Server > Issue Type: Bug > Components: Weld/CDI > Reporter: Pete Muir > Fix For: 6.0.0.CR1 > > -- 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

15 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2010