September 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBAS-8286) Wrong classloader used in InterceptorMethodHandler.readObject in JBoss AS

by Marius Bogoevici (JIRA)

[ https://jira.jboss.org/browse/JBAS-8286?page=com.atlassian.jira.plugin.sy... ] Marius Bogoevici updated JBAS-8286: ----------------------------------- Affects Version/s: TBD-6.x Not sure this is an issue - the test seems to force the usage of a certain classloader - however making sure that the stream is correctly set up is a responsibility of the application server. > Wrong classloader used in InterceptorMethodHandler.readObject in JBoss AS > ------------------------------------------------------------------------- > > Key: JBAS-8286 > URL: https://jira.jboss.org/browse/JBAS-8286 > Project: JBoss Application Server > Issue Type: Bug > Affects Versions: TBD-6.x > Reporter: Pete Muir > Assignee: Marius Bogoevici > Fix For: 6.0.0.CR1 > > > See org.jboss.weld.test.unit.interceptor.passivation.PassivationActivationTest.testPassivationAndActivation() > It looks to me like the classloader of jboss-interceptor (the classloader for the deployer) is used to deserialize the proxy, whilst the WeldImpl exists on the application classloader -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBAS-8342) EJB descriptor implementation must include support for remote business interfaces

by Marius Bogoevici (JIRA)

[ https://jira.jboss.org/browse/JBAS-8342?page=com.atlassian.jira.plugin.sy... ] Marius Bogoevici closed JBAS-8342. ---------------------------------- Resolution: Done > EJB descriptor implementation must include support for remote business interfaces > --------------------------------------------------------------------------------- > > Key: JBAS-8342 > URL: https://jira.jboss.org/browse/JBAS-8342 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Weld/CDI > Affects Versions: 6.0.0.M4 > Reporter: Marius Bogoevici > Assignee: Marius Bogoevici > Fix For: 6.0.0.CR1 > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBAS-8217) Simple war based ejb deployment does not work on JBoss 6.0M3

by Marius Bogoevici (JIRA)

[ https://jira.jboss.org/browse/JBAS-8217?page=com.atlassian.jira.plugin.sy... ] Marius Bogoevici commented on JBAS-8217: ---------------------------------------- Resolved after switching to the new EJB resolver SPI > Simple war based ejb deployment does not work on JBoss 6.0M3 > ------------------------------------------------------------- > > Key: JBAS-8217 > URL: https://jira.jboss.org/browse/JBAS-8217 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Weld/CDI > Environment: Snow Leopard 10.6.3, Java 6. > Reporter: Vladimir Blagojevic > Assignee: Marius Bogoevici > Fix For: 6.0.0.CR1 > > Attachments: weldint-64.zip > > > Have a simple war app with pojo ejb, trying to inject ejb field into a managed bean which is in turn accessed from a facelet. @EJB and @Inject dot not work on JBoss 6.0 M3. Attaching minimal example app. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBAS-8217) Simple war based ejb deployment does not work on JBoss 6.0M3

by Marius Bogoevici (JIRA)

[ https://jira.jboss.org/browse/JBAS-8217?page=com.atlassian.jira.plugin.sy... ] Marius Bogoevici closed JBAS-8217. ---------------------------------- > Simple war based ejb deployment does not work on JBoss 6.0M3 > ------------------------------------------------------------- > > Key: JBAS-8217 > URL: https://jira.jboss.org/browse/JBAS-8217 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Weld/CDI > Environment: Snow Leopard 10.6.3, Java 6. > Reporter: Vladimir Blagojevic > Assignee: Marius Bogoevici > Fix For: 6.0.0.CR1 > > Attachments: weldint-64.zip > > > Have a simple war app with pojo ejb, trying to inject ejb field into a managed bean which is in turn accessed from a facelet. @EJB and @Inject dot not work on JBoss 6.0 M3. Attaching minimal example app. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBAS-8217) Simple war based ejb deployment does not work on JBoss 6.0M3

by Marius Bogoevici (JIRA)

[ https://jira.jboss.org/browse/JBAS-8217?page=com.atlassian.jira.plugin.sy... ] Marius Bogoevici resolved JBAS-8217. ------------------------------------ Fix Version/s: 6.0.0.CR1 (was: 6.0.0.Final) Resolution: Done > Simple war based ejb deployment does not work on JBoss 6.0M3 > ------------------------------------------------------------- > > Key: JBAS-8217 > URL: https://jira.jboss.org/browse/JBAS-8217 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Weld/CDI > Environment: Snow Leopard 10.6.3, Java 6. > Reporter: Vladimir Blagojevic > Assignee: Marius Bogoevici > Fix For: 6.0.0.CR1 > > Attachments: weldint-64.zip > > > Have a simple war app with pojo ejb, trying to inject ejb field into a managed bean which is in turn accessed from a facelet. @EJB and @Inject dot not work on JBoss 6.0 M3. Attaching minimal example app. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2483) get HTTP 500 - Default page does not exist error after restarted portal server

by jay ZHAO (JIRA)

get HTTP 500 - Default page does not exist error after restarted portal server ------------------------------------------------------------------------------- Key: JBPORTAL-2483 URL: https://jira.jboss.org/browse/JBPORTAL-2483 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Core Affects Versions: 2.7.2 Final Environment: RHEL 5 and XP Reporter: jay ZHAO Fix For: 2.7.2 Final >From admin account change default page to a newly created portal page, and then logout, restart the portal server, i get get HTTP 500 - Default page does not exist error: java.lang.IllegalStateException: Default page does not exist org.jboss.portal.core.model.portal.DefaultPortalCommandFactory.doMapping(DefaultPortalCommandFactory.java:85) org.jboss.portal.core.controller.Controller.handle(Controller.java:252) org.jboss.portal.server.RequestControllerDispatcher.invoke(RequestControllerDispatcher.java:51) org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:131) org.jboss.portal.core.cms.aspect.IdentityBindingInterceptor.invoke(IdentityBindingInterceptor.java:47) org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38) org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) org.jboss.portal.server.aspects.server.ContentTypeInterceptor.invoke(ContentTypeInterceptor.java:68) org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38) org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) org.jboss.portal.core.aspects.server.PortalContextPathInterceptor.invoke(PortalContextPathInterceptor.java:45) org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38) org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) org.jboss.portal.core.aspects.server.LocaleInterceptor.invoke(LocaleInterceptor.java:96) org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38) org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) org.jboss.portal.core.aspects.server.UserInterceptor.invoke(UserInterceptor.java:196) org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38) org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) org.jboss.portal.server.aspects.server.SignOutInterceptor.invoke(SignOutInterceptor.java:98) org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38) org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) org.jboss.portal.core.impl.api.user.UserEventBridgeTriggerInterceptor.invoke(UserEventBridgeTriggerInterceptor.java:65) org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38) org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) org.jboss.portal.core.aspects.server.IdentityCacheInterceptor.invoke(IdentityCacheInterceptor.java:68) org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38) org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) org.jboss.portal.core.aspects.server.TransactionInterceptor.org$jboss$portal$core$aspects$server$TransactionInterceptor$invoke$aop(TransactionInterceptor.java:49) org.jboss.portal.core.aspects.server.TransactionInterceptor$invoke_N5143606530999904530.invokeNext(TransactionInterceptor$invoke_N5143606530999904530.java) org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79) org.jboss.aspects.tx.TxInterceptor$RequiresNew.invoke(TxInterceptor.java:253) org.jboss.portal.core.aspects.server.TransactionInterceptor$invoke_N5143606530999904530.invokeNext(TransactionInterceptor$invoke_N5143606530999904530.java) org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79) org.jboss.aspects.tx.TxInterceptor$RequiresNew.invoke(TxInterceptor.java:262) org.jboss.portal.core.aspects.server.TransactionInterceptor$invoke_N5143606530999904530.invokeNext(TransactionInterceptor$invoke_N5143606530999904530.java) org.jboss.portal.core.aspects.server.TransactionInterceptor.invoke(TransactionInterceptor.java) org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38) org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) org.jboss.portal.server.aspects.LockInterceptor$InternalLock.invoke(LockInterceptor.java:69) org.jboss.portal.server.aspects.LockInterceptor.invoke(LockInterceptor.java:130) org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) org.jboss.portal.common.invocation.Invocation.invoke(Invocation.java:157) org.jboss.portal.server.servlet.PortalServlet.service(PortalServlet.java:252) javax.servlet.http.HttpServlet.service(HttpServlet.java:803) org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-2425) Add support for "From", "Accumulate" and "Collect" to Business Rule Editor

by Pablo Nussembaum (JIRA)

Add support for "From", "Accumulate" and "Collect" to Business Rule Editor -------------------------------------------------------------------------- Key: JBRULES-2425 URL: https://jira.jboss.org/jira/browse/JBRULES-2425 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-guvnor Reporter: Pablo Nussembaum Assignee: Mark Proctor Add support to complex conditions elements to guvnor -- 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, 4 months

2
5
0 / 0

[JBoss JIRA] Updated: (JBAS-8280) interceptors/decorators for EJBs

by Marius Bogoevici (JIRA)

[ https://jira.jboss.org/browse/JBAS-8280?page=com.atlassian.jira.plugin.sy... ] Marius Bogoevici updated JBAS-8280: ----------------------------------- Summary: interceptors/decorators for EJBs (was: interceptors/decorators for EJBs which are not web beans) Description: EJBs must be decorated and intercepted (as per the CDI spec) if they are deployed in a CDI-enabled archive > interceptors/decorators for EJBs > -------------------------------- > > Key: JBAS-8280 > URL: https://jira.jboss.org/browse/JBAS-8280 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Weld/CDI > Reporter: Gavin King > Assignee: Marius Bogoevici > Fix For: 6.0.0.CR1 > > > EJBs must be decorated and intercepted (as per the CDI spec) if they are deployed in a CDI-enabled archive -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-7210) JBossContextConfig needs to be isolated from the war class loader

by Scott M Stark (JIRA)

JBossContextConfig needs to be isolated from the war class loader ----------------------------------------------------------------- Key: JBAS-7210 URL: https://jira.jboss.org/jira/browse/JBAS-7210 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: ClassLoading, Web (Tomcat) service Affects Versions: JBossAS-5.1.0.GA Reporter: Scott M Stark Assignee: Scott M Stark The parsing of the context.xml by the JBossContextConfig class is using the tccl which causes problems when the war app has tried to load its own xml parser. -- 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, 4 months

9
11
0 / 0

[JBoss JIRA] Assigned: (EJBTHREE-503) EJB2.1 Style Message Driven Bean Lifecycle Methods Not Called

by Carlo de Wolf (JIRA)

[ https://jira.jboss.org/browse/EJBTHREE-503?page=com.atlassian.jira.plugin... ] Carlo de Wolf reassigned EJBTHREE-503: -------------------------------------- Assignee: Carlo de Wolf > EJB2.1 Style Message Driven Bean Lifecycle Methods Not Called > ------------------------------------------------------------- > > Key: EJBTHREE-503 > URL: https://jira.jboss.org/browse/EJBTHREE-503 > Project: EJB 3.0 > Issue Type: Bug > Affects Versions: EJB 3.0 RC6 - PFD > Environment: JBoss 4.0.4.CR2 EJB3.0 Profile > Reporter: Darran Lofthouse > Assignee: Carlo de Wolf > > For a message driven bean that implements the 'javax.ejb.MessageDrivenBean' interface the lifecycle callback methods are not called as required. > The first method to be called is onMessage when a message is received, the calls to ejbCreate and setMessageDrivenContext are skipped. -- 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, 4 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2010