July 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (EJBTHREE-191) servlet initialization happens before EJB startup

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-191?page=all ] Dimitris Andreadis updated EJBTHREE-191: ---------------------------------------- Fix Version/s: AS 4.2.2.GA (was: AS 4.2.1.GA) > servlet initialization happens before EJB startup > ------------------------------------------------- > > Key: EJBTHREE-191 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-191 > Project: EJB 3.0 > Issue Type: Bug > Reporter: Bill Burke > Fix For: AS 4.2.2.GA > > -- 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

17 years

1
0
0 / 0

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

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-322?page=all ] Dimitris Andreadis updated EJBTHREE-322: ---------------------------------------- Fix Version/s: AS 4.2.2.GA (was: AS 4.2.1.GA) > 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 RC3, EJB 3.0 RC1, EJB 3.0 RC2 > Reporter: Bill Burke > Assigned To: Bill Burke > Fix For: AS 4.2.2.GA > > > 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

17 years

1
0
0 / 0

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

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-342?page=all ] Dimitris Andreadis updated EJBTHREE-342: ---------------------------------------- Fix Version/s: AS 4.2.2.GA (was: AS 4.2.1.GA) > 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: AS 4.2.2.GA > > > 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

17 years

1
0
0 / 0

[JBoss JIRA] Updated: (EJBTHREE-305) Port EJB 2.1 tests to EJB 3.0 where appropriate

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-305?page=all ] Dimitris Andreadis updated EJBTHREE-305: ---------------------------------------- Fix Version/s: AS 4.2.2.GA (was: AS 4.2.1.GA) > Port EJB 2.1 tests to EJB 3.0 where appropriate > ----------------------------------------------- > > Key: EJBTHREE-305 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-305 > Project: EJB 3.0 > Issue Type: Task > Affects Versions: EJB 3.0 RC4 - PFD > Reporter: Bill Burke > Assigned To: William DeCoste > Fix For: AS 4.2.2.GA > > -- 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

17 years

1
0
0 / 0

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

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-421?page=all ] Dimitris Andreadis updated EJBTHREE-421: ---------------------------------------- Fix Version/s: AS 4.2.2.GA (was: AS 4.2.1.GA) > 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: AS 4.2.2.GA > > -- 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

17 years

1
0
0 / 0

[JBoss JIRA] Updated: (EJBTHREE-344) Deployment should fail for resource injection to both field and method

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-344?page=all ] Dimitris Andreadis updated EJBTHREE-344: ---------------------------------------- Fix Version/s: AS 4.2.2.GA (was: AS 4.2.1.GA) > Deployment should fail for resource injection to both field and method > ---------------------------------------------------------------------- > > Key: EJBTHREE-344 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-344 > Project: EJB 3.0 > Issue Type: Bug > Environment: org.jboss.ejb3.test.naming.unit.BadInjectionsUnitTestCase > Reporter: Scott M Stark > Assigned To: William DeCoste > Fix For: AS 4.2.2.GA > > > I belive the indicated BadInjectionsUnitTestCase should be failing to deploy due to the attempt to inject an env-entry via both a field and method annotation. The ejb-jar.xml key env-entry value is not being injected via either mechanism it appears. -- 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

17 years

1
0
0 / 0

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

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-564?page=all ] Dimitris Andreadis updated EJBTHREE-564: ---------------------------------------- Fix Version/s: AS 4.2.2.GA (was: AS 4.2.1.GA) > 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: AS 4.2.2.GA > > > 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

17 years

1
0
0 / 0

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

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-509?page=all ] Dimitris Andreadis updated EJBTHREE-509: ---------------------------------------- Fix Version/s: AS 4.2.2.GA (was: AS 4.2.1.GA) > EJB 3.0 persistense manager unit name is not comming up when deploying entity bean > ---------------------------------------------------------------------------------- > > Key: EJBTHREE-509 > URL: http://jira.jboss.com/jira/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: AS 4.2.2.GA > > > 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: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years

1
0
0 / 0

[JBoss JIRA] Updated: (EJBTHREE-477) Implement @WebServiceRef and <service-ref>

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-477?page=all ] Dimitris Andreadis updated EJBTHREE-477: ---------------------------------------- Fix Version/s: AS 4.2.2.GA (was: AS 4.2.1.GA) > Implement @WebServiceRef and <service-ref> > ------------------------------------------ > > Key: EJBTHREE-477 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-477 > Project: EJB 3.0 > Issue Type: Task > Reporter: Bill Burke > Assigned To: William DeCoste > Priority: Critical > Fix For: AS 4.2.2.GA > > > This will be fun!!!! > Take a look at code in EJB 2.1 container. DO NOT USE THAT CODE DIRECTLY. I want to start removing dependencies on that code. You can also work with WS team on this too. This should be a HIG PRIORITY task. -- 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

17 years

1
0
0 / 0

[JBoss JIRA] Created: (JGRP-547) ReplicatedHashMap does not synchonized state with the members (CSV tips)

by Dipak Kothari (JIRA)

ReplicatedHashMap does not synchonized state with the members (CSV tips) ------------------------------------------------------------------------ Key: JGRP-547 URL: http://jira.jboss.com/jira/browse/JGRP-547 Project: JGroups Issue Type: Bug Reporter: Dipak Kothari Assigned To: Bela Ban Attachments: loadtest.zip As per the message trail in the JGroup Help forum, starting many services concurrently causes the state not to synchronize - have noticed more then one cordinator. When the merge happens the state is not synchronized or I don't know how to. I have attached example code that causes this behaviour on my pc. The JGroup jar contains source from 2.5cr1 release with the ReplicatedHashMap added in. The loadtest package contains my code, pretty self explainatory -- 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

17 years

2
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2007