September 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (EJBTHREE-12) EJB ENC must be java:comp/env currently it is java.ejb/comp/env

by Bill Burke (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-12?page=all ] Bill Burke updated EJBTHREE-12: ------------------------------- Fix Version/s: EJB 3.0 RC10 - FD (was: EJB 3.0 RC9 - FD) > EJB ENC must be java:comp/env currently it is java.ejb/comp/env > ---------------------------------------------------------------- > > Key: EJBTHREE-12 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-12 > Project: EJB 3.0 > Issue Type: Feature Request > Affects Versions: Preview 5 > Reporter: Bill Burke > Assigned To: Bill Burke > Fix For: EJB 3.0 RC10 - FD > > -- 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

19 years, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (EJBTHREE-421) Put FlushMode.NEVER back on track through @FlushMode, at least in a proprietary manner

by Bill Burke (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-421?page=all ] Bill Burke updated EJBTHREE-421: -------------------------------- Fix Version/s: EJB 3.0 RC10 - FD (was: EJB 3.0 RC9 - FD) > Put FlushMode.NEVER back on track through @FlushMode, at least in a proprietary manner > -------------------------------------------------------------------------------------- > > Key: EJBTHREE-421 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-421 > Project: EJB 3.0 > Issue Type: Feature Request > Reporter: Emmanuel Bernard > Fix For: EJB 3.0 RC10 - FD > > -- 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

19 years, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (EJBTHREE-414) Support Nested SFSB in clustered environment

by Bill Burke (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-414?page=all ] Bill Burke updated EJBTHREE-414: -------------------------------- Fix Version/s: EJB 3.0 RC10 - FD (was: EJB 3.0 RC9 - FD) > Support Nested SFSB in clustered environment > -------------------------------------------- > > Key: EJBTHREE-414 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-414 > Project: EJB 3.0 > Issue Type: Feature Request > Reporter: Bill Burke > Assigned To: Bill Burke > Fix For: EJB 3.0 RC10 - FD > > -- 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

19 years, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (EJBTHREE-575) Access configuration attributes through JMX

by Bill Burke (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-575?page=all ] Bill Burke updated EJBTHREE-575: -------------------------------- Fix Version/s: EJB 3.0 RC10 - FD (was: EJB 3.0 RC9 - FD) > Access configuration attributes through JMX > ------------------------------------------- > > Key: EJBTHREE-575 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-575 > Project: EJB 3.0 > Issue Type: Feature Request > Affects Versions: EJB 3.0 RC7 - FD > Reporter: Darran Lofthouse > Fix For: EJB 3.0 RC10 - FD > > > This might be more appropriate split into a number of tasks but for the moment I am raising it as a single issue. > There are a number of properties that can be set on message driven beans using activation config properties e.g. 'maxPoolSize'. After deployment there is not a mechanism to check that the correct properties have been applied. It would be good to be able to inspect the configuration values using JMX. > Using the @PoolClass annotation it is possible to configure the pool that is used for the EJB, it would also be good if this configuration information could also be made available using JMX. > For the configuration items it would also be good if the attributes could be updated using JMX. > Finally providing status information such as current pool sizes through JMX would also help users check the configuration they have selected is appropriate. -- 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

19 years, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (EJBTHREE-372) MDB Management features

by Bill Burke (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-372?page=all ] Bill Burke updated EJBTHREE-372: -------------------------------- Fix Version/s: EJB 3.0 RC10 - FD (was: EJB 3.0 RC9 - FD) > MDB Management features > ----------------------- > > Key: EJBTHREE-372 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-372 > Project: EJB 3.0 > Issue Type: Task > Affects Versions: EJB 3.0 RC3 > Reporter: Kabir Khan > Assigned To: William DeCoste > Fix For: EJB 3.0 RC10 - FD > > > Implement startDelivery(), stopDelivery(), setMaxMessages(int) and adjust the MDB pool size for MDBs -- 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

19 years, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (EJBTHREE-27) Allowed methods

by Bill Burke (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-27?page=all ] Bill Burke updated EJBTHREE-27: ------------------------------- Fix Version/s: EJB 3.0 RC10 - FD (was: EJB 3.0 RC9 - FD) > Allowed methods > --------------- > > Key: EJBTHREE-27 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-27 > Project: EJB 3.0 > Issue Type: Feature Request > Affects Versions: Preview 5 > Reporter: Bill Burke > Assigned To: Bill Burke > Fix For: EJB 3.0 RC10 - FD > > > EJB specification has semanatics for what methods can be called when. -- 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

19 years, 8 months

1
0
0 / 0

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

by Bill Burke (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-564?page=all ] Bill Burke updated EJBTHREE-564: -------------------------------- Fix Version/s: EJB 3.0 RC10 - FD (was: EJB 3.0 RC9 - FD) > Inconsistent results in ConsumerUnitTestCase > -------------------------------------------- > > Key: EJBTHREE-564 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-564 > Project: EJB 3.0 > Issue Type: Bug > Environment: org.jboss.ejb3.test.consumer.unit.ConsumerUnitTestCase > Reporter: Scott M Stark > Assigned To: William DeCoste > Fix For: EJB 3.0 RC10 - FD > > > 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: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (EJBTHREE-124) @PersistenceContext(EXTENDED) should follow new Spec defined rules

by Bill Burke (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-124?page=all ] Bill Burke updated EJBTHREE-124: -------------------------------- Fix Version/s: (was: EJB 3.0 RC9 - FD) EJB 3.0 RC10 - FD > @PersistenceContext(EXTENDED) should follow new Spec defined rules > ------------------------------------------------------------------ > > Key: EJBTHREE-124 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-124 > Project: EJB 3.0 > Issue Type: Feature Request > Affects Versions: Preview 5 > Reporter: Bill Burke > Fix For: EJB 3.0 RC10 - FD > > > I don't yet follow all the spec defined rules for @PersistenceContext(EXTENDED) -- 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

19 years, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (EJBTHREE-342) Unify configuration file names and bootstrap

by Bill Burke (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-342?page=all ] Bill Burke updated EJBTHREE-342: -------------------------------- Fix Version/s: EJB 3.0 RC10 - FD (was: EJB 3.0 RC9 - FD) > Unify configuration file names and bootstrap > -------------------------------------------- > > Key: EJBTHREE-342 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-342 > Project: EJB 3.0 > Issue Type: Bug > Reporter: Christian Bauer > Assigned To: Bill Burke > Fix For: EJB 3.0 RC10 - FD > > > The microcontainer can be booted with StandaloneBootstrap, and it searches for jboss-beans.xml in / and META-INF. > The E-EJB3 container is booted with EJB3StandaloneBootstrap, which searches for embedded-jboss-beans.xml in / and supports a "basepath" argument. > Unify these two bootstrap classes. Wishlist: > - sensible default name for the configuration file ("jboss-beans.xml" sounds good) > - searches in default locations (/ and META-INF) > - supports parameters to completely override not only the "basepath", but the full location of the configuration file > The EJB3StandaloneBootstrap should _extend_ the StandaloneBootstrap, not reimplement it. The current situation makes documentation and explanation unecessarily difficult. -- 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

19 years, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (EJBTHREE-322) implement discarding rules

by Bill Burke (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-322?page=all ] Bill Burke updated EJBTHREE-322: -------------------------------- Fix Version/s: EJB 3.0 RC10 - FD (was: EJB 3.0 RC9 - FD) > implement discarding rules > -------------------------- > > Key: EJBTHREE-322 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-322 > Project: EJB 3.0 > Issue Type: Bug > Affects Versions: EJB 3.0 RC1, EJB 3.0 RC2, EJB 3.0 RC3 > Reporter: Bill Burke > Assigned To: Bill Burke > Fix For: EJB 3.0 RC10 - FD > > > we are not discarding EJB instances where appropriate. -- 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

19 years, 8 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 2006