September 2010 - jboss-jira - Jboss List Archives

[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

15 years, 10 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

15 years, 10 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

15 years, 10 months

1
0
0 / 0

[JBoss JIRA] Resolved: (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 resolved EJBTHREE-503. ------------------------------------ Resolution: Duplicate Issue > 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

15 years, 10 months

1
0
0 / 0

[JBoss JIRA] Resolved: (EJBTHREE-564) Inconsistent results in ConsumerUnitTestCase

by Carlo de Wolf (JIRA)

[ https://jira.jboss.org/browse/EJBTHREE-564?page=com.atlassian.jira.plugin... ] Carlo de Wolf resolved EJBTHREE-564. ------------------------------------ Resolution: Out of Date This issue is reported against a version which is no longer maintained, which means that it will not receive a fix. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of JBoss EJB 3 please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. > Inconsistent results in ConsumerUnitTestCase > -------------------------------------------- > > Key: EJBTHREE-564 > URL: https://jira.jboss.org/browse/EJBTHREE-564 > Project: EJB 3.0 > Issue Type: Bug > Environment: org.jboss.ejb3.test.consumer.unit.ConsumerUnitTestCase > Reporter: Scott M Stark > Assignee: William DeCoste > Fix For: Branch_4_2 > > > If I run the ConsumerUnitTestCase multiple times I start seeing failures due to method invocation order it seems. > [starksm@banshee9100 ejb3]$ ant -buildfile build-test.xml -Dtest=consumer test > Buildfile: build-test.xml > init: > test: > test-with-jvmargs: > [delete] Deleting: C:\cvs\JBoss4.0\jboss-4.0.x\ejb3\output\log\test.log > [junit] Running org.jboss.ejb3.test.consumer.unit.ConsumerUnitTestCase > [starksm@banshee9100 ejb3]$ ant -buildfile build-test.xml -Dtest=consumer test > Buildfile: build-test.xml > init: > test: > test-with-jvmargs: > [delete] Deleting: C:\cvs\JBoss4.0\jboss-4.0.x\ejb3\output\log\test.log > [junit] Running org.jboss.ejb3.test.consumer.unit.ConsumerUnitTestCase > [junit] Tests run: 6, Failures: 0, Errors: 0, Time elapsed: 16.344 sec > BUILD SUCCESSFUL > Total time: 21 seconds > [starksm@banshee9100 ejb3]$ ant -buildfile build-test.xml -Dtest=consumer test > Buildfile: build-test.xml > init: > test: > test-with-jvmargs: > [delete] Deleting: C:\cvs\JBoss4.0\jboss-4.0.x\ejb3\output\log\test.log > [junit] Running org.jboss.ejb3.test.consumer.unit.ConsumerUnitTestCase > [junit] Tests run: 6, Failures: 1, Errors: 0, Time elapsed: 14.359 sec > [junit] Test org.jboss.ejb3.test.consumer.unit.ConsumerUnitTestCase FAILED > BUILD SUCCESSFUL > Total time: 19 seconds > [starksm@banshee9100 ejb3]$ ant -buildfile build-test.xml -Dtest=consumer test > Buildfile: build-test.xml > init: > test: > test-with-jvmargs: > [delete] Deleting: C:\cvs\JBoss4.0\jboss-4.0.x\ejb3\output\log\test.log > [junit] Running org.jboss.ejb3.test.consumer.unit.ConsumerUnitTestCase > [junit] Tests run: 6, Failures: 1, Errors: 0, Time elapsed: 14.86 sec > [junit] Test org.jboss.ejb3.test.consumer.unit.ConsumerUnitTestCase FAILED > BUILD SUCCESSFUL > Total time: 19 seconds > <testcase classname="org.jboss.ejb3.test.consumer.unit.ConsumerUnitTestCase" name="testDeploymentDescriptorQueueXA" time="2.032"> > <failure message="expected:<...1> but was:<...2>" type="junit.framework.ComparisonFailure">junit.framework.ComparisonFailure: expected:<...1> but was:<...2> > at org.jboss.ejb3.test.consumer.unit.ConsumerUnitTestCase.testDeploymentDescriptorQueueXA(ConsumerUnitTestCase.java:151) > at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22) > at junit.extensions.TestSetup$1.protect(TestSetup.java:19) > at junit.extensions.TestSetup.run(TestSetup.java:23) > </failure> -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1015) ServiceDelegateWrapper should delegate MBeanRegistration and NotificationEmitter calls

by Galder Zamarreno (JIRA)

ServiceDelegateWrapper should delegate MBeanRegistration and NotificationEmitter calls -------------------------------------------------------------------------------------- Key: EJBTHREE-1015 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1015 Project: EJB 3.0 Issue Type: Feature Request Components: EJB3 Extensions Affects Versions: AS 4.2.1.GA Reporter: Galder Zamarreno Fix For: AS 4.2.2.GA ServiceDelegateWrapper should delegate MBeanRegistration and NotificationEmitter calls to EJB3 Services if users made their EJB3 services implement these interfaces. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

2
5
0 / 0

[JBoss JIRA] Created: (EJBTHREE-754) isCallerInRole checks should go through JACC layer (if JACC is configured)

by Anil Saldhana (JIRA)

isCallerInRole checks should go through JACC layer (if JACC is configured) -------------------------------------------------------------------------- Key: EJBTHREE-754 URL: http://jira.jboss.com/jira/browse/EJBTHREE-754 Project: EJB 3.0 Issue Type: Task Components: Security Affects Versions: EJB 3.0 RC9 - FD Reporter: Anil Saldhana Assigned To: Scott M Stark Fix For: EJB 3.0 RC10 - FD Since Scott is going to review the ejb3 JACC implementation, I am assigning this issue to Scott. The EJBContext.isCallerInRole checks need to go through the jacc layer, if the user has configured jacc. I am not sure what the best way to tell the xxxContext layer to use jacc helper if user desires. Maybe a simple system property may do it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

3
6
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1132) EJB3 tests should not assume server is bound to localhost

by Brian Stansberry (JIRA)

EJB3 tests should not assume server is bound to localhost --------------------------------------------------------- Key: EJBTHREE-1132 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1132 Project: EJB 3.0 Issue Type: Task Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Minor Fix For: AS 5.0.0.Beta3, Branch_4_2 A number of EJB3 tests are hard coding localhost in various URLs. Should be the value returned by system property jbosstest.server.host, which build-test.xml should set to the value of ant property ${node0}. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

2
3
0 / 0

[JBoss JIRA] Resolved: (EJBTHREE-509) EJB 3.0 persistense manager unit name is not comming up when deploying entity bean

by Carlo de Wolf (JIRA)

[ https://jira.jboss.org/browse/EJBTHREE-509?page=com.atlassian.jira.plugin... ] Carlo de Wolf resolved EJBTHREE-509. ------------------------------------ Resolution: Out of Date This issue is reported against a version which is no longer maintained, which means that it will not receive a fix. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of JBoss EJB 3 please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. > EJB 3.0 persistense manager unit name is not comming up when deploying entity bean > ---------------------------------------------------------------------------------- > > Key: EJBTHREE-509 > URL: https://jira.jboss.org/browse/EJBTHREE-509 > Project: EJB 3.0 > Issue Type: Bug > Components: EJB3 Extensions > Affects Versions: EJB 3.0 RC5 - PFD > Environment: linux, jboss 4.0.2 > Reporter: Amit Chauhan > Priority: Minor > Fix For: Branch_4_2 > > > trying to implement the tutorial example provided at http://docs.jboss.org/ejb3/app-servers/tutorials/entity/entity.html -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Resolved: (EJBTHREE-217) The container should Instruments Hibernate classes

by Carlo de Wolf (JIRA)

[ https://jira.jboss.org/browse/EJBTHREE-217?page=com.atlassian.jira.plugin... ] Carlo de Wolf resolved EJBTHREE-217. ------------------------------------ Resolution: Out of Date This issue is reported against a version which is no longer maintained, which means that it will not receive a fix. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of JBoss EJB 3 please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. > The container should Instruments Hibernate classes > -------------------------------------------------- > > Key: EJBTHREE-217 > URL: https://jira.jboss.org/browse/EJBTHREE-217 > Project: EJB 3.0 > Issue Type: Feature Request > Components: EJB3 Extensions > Affects Versions: EJB 3.0 Beta 1 > Reporter: Emmanuel Bernard > Assignee: Bill Burke > Priority: Minor > Fix For: Branch_4_2 > > > Right now, the user has to instrument Hibernate classes itself through a InstrumentAnt task to enable some features such as property level lazy loading > It'd be cool if the container execute the same job at class load time in an automatic manner. > http://www.hibernate.org/hib_docs/v3/reference/en/html_single/#performanc... -- 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, 10 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 September 2010