October 2007 - jboss-jira - Jboss List Archives

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

by Carlo de Wolf (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-342?page=all ] Carlo de Wolf updated EJBTHREE-342: ----------------------------------- Fix Version/s: Branch_4_2 (was: AS 4.2.2.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: Branch_4_2 > > > 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

16 years, 11 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 Carlo de Wolf (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-421?page=all ] Carlo de Wolf updated EJBTHREE-421: ----------------------------------- Fix Version/s: Branch_4_2 (was: AS 4.2.2.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: Branch_4_2 > > -- 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

16 years, 11 months

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 Carlo de Wolf (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-509?page=all ] Carlo de Wolf updated EJBTHREE-509: ----------------------------------- Fix Version/s: Branch_4_2 (was: AS 4.2.2.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: 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: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 11 months

1
0
0 / 0

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

by Carlo de Wolf (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-564?page=all ] Carlo de Wolf updated EJBTHREE-564: ----------------------------------- Fix Version/s: Branch_4_2 (was: AS 4.2.2.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: 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: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1772) Security fixes for JBoss Portal 2.6.2

by Magesh Kumar B (JIRA)

Security fixes for JBoss Portal 2.6.2 ------------------------------------- Key: JBPORTAL-1772 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1772 Project: JBoss Portal Issue Type: Support Patch Security Level: Public (Everyone can see) Components: Portal Security Affects Versions: 2.6.2 Final Reporter: Magesh Kumar B Assigned To: Julien Viet The patch contains fixes for the following issues: [JBPORTAL-1741] PortalURL security not honoured [JBPORTAL-1481] Reimplement portal security interface without JACC -- 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

16 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1771) Add support for event listener binding to windows in admin interface

by Chris Laprun (JIRA)

Add support for event listener binding to windows in admin interface -------------------------------------------------------------------- Key: JBPORTAL-1771 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1771 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal Core Admin Affects Versions: 2.6.2 Final, 2.8 Final Reporter: Chris Laprun Assigned To: Chris Laprun Priority: Minor Fix For: 2.6.3 Final, 2.8 Final -- 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

16 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-1285) Time Machine to allow setting of "now" effective current time in Rule

by Michael Neale (JIRA)

Time Machine to allow setting of "now" effective current time in Rule --------------------------------------------------------------------- Key: JBRULES-1285 URL: http://jira.jboss.com/jira/browse/JBRULES-1285 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.0.2 Reporter: Michael Neale Assigned To: Michael Neale Fix For: 4.1.0 This is needed for testing effective dating. -- 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

16 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBCACHE-1203) putForExternalRead replicates when INVALIDATION used

by Brian Stansberry (JIRA)

putForExternalRead replicates when INVALIDATION used ---------------------------------------------------- Key: JBCACHE-1203 URL: http://jira.jboss.com/jira/browse/JBCACHE-1203 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Manik Surtani Fix For: 2.1.0.BETA1 If you configure INVALIDATION and call putForExternalRead, the value will be replicated around the cluster. There should be no impact on other cluster members at all. The various org.jboss.cache.api.pfer/PFERxxxInvalidation* tests show the problem. -- 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

16 years, 11 months

2
3
0 / 0

[JBoss JIRA] Created: (JBCACHE-1200) Node removal with invalidation leaves child data accessible

by Brian Stansberry (JIRA)

Node removal with invalidation leaves child data accessible ----------------------------------------------------------- Key: JBCACHE-1200 URL: http://jira.jboss.com/jira/browse/JBCACHE-1200 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.1.0.BETA1 Reporter: Brian Stansberry Assigned To: Manik Surtani Priority: Critical Fix For: 2.1.0.CR1 With invalidation, when a node that has children is removed, on remote caches the data in the children is still visible; e..g cache1.put(childFqn, key, value); cache1.removeNode(parentFqn); // This assertion fails assertNull(cache2.get(childFqn, key)); InvalidationInterceptorTest.testPessimisticNodeRemoval() and testOptimisticNodeRemoval() have been modified to show this issue. This is a significant problem for the Hibernate/JBC integration -- 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

16 years, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (JBCACHE-1199) Update InvalidatorInterceptorTest to use Node.isValid()

by Brian Stansberry (JIRA)

Update InvalidatorInterceptorTest to use Node.isValid() ------------------------------------------------------- Key: JBCACHE-1199 URL: http://jira.jboss.com/jira/browse/JBCACHE-1199 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.1.0.BETA1 Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Minor Fix For: 2.1.0.GA InvalidatorInterceptorTest.testOptimisticNodeRemoval() and testPessimisticNodeRemoval() are using a clunky method of checking the state of a remotely removed node. See the forum link. Need to replace with a call to isValid() whenever that is implemented. -- 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

16 years, 11 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2007