August 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBCACHE-1398) Provide a way to remove nodes when evicting

by Manik Surtani (JIRA)

Provide a way to remove nodes when evicting ------------------------------------------- Key: JBCACHE-1398 URL: https://jira.jboss.org/jira/browse/JBCACHE-1398 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Eviction Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 3.0.0.BETA1, 3.0.0.GA For details, see eviction redesign in JBCACHE-1411 -- 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

17 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-334) XML created Annotations should be removed from the INSTANCE metadata when the bean is uninstalled

by Adrian Brock (JIRA)

XML created Annotations should be removed from the INSTANCE metadata when the bean is uninstalled ------------------------------------------------------------------------------------------------- Key: JBMICROCONT-334 URL: https://jira.jboss.org/jira/browse/JBMICROCONT-334 Project: JBoss MicroContainer Issue Type: Bug Components: Kernel Reporter: Adrian Brock Fix For: JBossMC.2.0.0.CR1 See MutableMetaData testcase The annotations loaded from the BeanMetaData into the INSTANCE/mutable metadata should be removed at uninstall. -- 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

17 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-5832) Add Facelets logging bridge to AS

by Stan Silvert (JIRA)

Add Facelets logging bridge to AS --------------------------------- Key: JBAS-5832 URL: https://jira.jboss.org/jira/browse/JBAS-5832 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JSF, Logging Affects Versions: JBossAS-5.0.0.CR1 Reporter: Stan Silvert Assignee: Stan Silvert Fix For: JBossAS-5.0.0.CR2 Most JSF applications these days use Facelets. However, like Mojarra (JSF RI), Facelets uses java.util.logging which makes our Log4J messages look funny. We need to check if Facelets is present. If so, we should convert the Facelets JUL messages to Log4J in the same manner we do for Mojarra. -- 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

17 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (JBCACHE-1397) AsyncCacheLoader to use multiple threads when writing to loader asynchronously

by Manik Surtani (JIRA)

AsyncCacheLoader to use multiple threads when writing to loader asynchronously ------------------------------------------------------------------------------ Key: JBCACHE-1397 URL: https://jira.jboss.org/jira/browse/JBCACHE-1397 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Cache loaders Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 3.0.0.BETA1, 3.0.0.GA Specified using the cache.async.threadPoolSize property, defaulting to 1. -- 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

17 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBCACHE-1108) Move CacheListeners to their own thread pool

by Jason T. Greene (JIRA)

Move CacheListeners to their own thread pool -------------------------------------------- Key: JBCACHE-1108 URL: http://jira.jboss.com/jira/browse/JBCACHE-1108 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Reporter: Jason T. Greene Assigned To: Manik Surtani Fix For: 2.0.0.CR3 User CacheListeners should be dispatched in their own thread pool to prevent reentrancy problems and delays on cache operations. Evection listeners should still be executed in the app thread. -Jason -- 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, 11 months

2
8
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-330) ScopeInfo should use the existing Mutable metadata if it already exists

by Adrian Brock (JIRA)

ScopeInfo should use the existing Mutable metadata if it already exists ----------------------------------------------------------------------- Key: JBMICROCONT-330 URL: https://jira.jboss.org/jira/browse/JBMICROCONT-330 Project: JBoss MicroContainer Issue Type: Bug Reporter: Adrian Brock Fix For: JBossMC.2.0.0.CR1 Currently the AbstractScopeInfo class is always creating a new Mutable MetaMeta context within the MDR. This would cause a problem where the scope has already been constructed, e.g. by the deployers. public void addMetaData(MutableMetaDataRepository repository, ControllerContext context) { this.repository = repository; ScopeKey scope = getMutableScope(); // Needs a check here for already exists - see the version of getMutableMetaData in AbstractDeploymentContext MemoryMetaDataLoader mutable = new MemoryMetaDataLoader(scope); repository.addMetaDataRetrieval(mutable); addMetaData(repository, context, mutable); } Similarly ScopeInfo::removeMetaData(), should not be removing MDR contexts it didn't construct. -- 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

17 years, 11 months

1
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1451) MDB.getActivationConfigProperties needs to validate that a destiation-type property exists

by Scott M Stark (JIRA)

MDB.getActivationConfigProperties needs to validate that a destiation-type property exists ------------------------------------------------------------------------------------------ Key: EJBTHREE-1451 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1451 Project: EJB 3.0 Issue Type: Bug Components: core Affects Versions: AS 5.0.0.CR1 Environment: com.sun.ts.tests.ejb30.bb.mdb.dest.optional.Client.test1 Reporter: Scott M Stark Fix For: AS 5.0.0.CR2 JBCTS-604 is failing to deploy because the jms activation needs to have a message destination type, but this not a required piece of metadata in javaee5. The attached patch allows the deployment to work, and the test passes. See the dev forum thread if there is a need to reject or change the patch. -- 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

17 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBDEPLOY-69) BeanMetaDataDeployer is not initializing the KernelScope from the deployment component scope

by Adrian Brock (JIRA)

BeanMetaDataDeployer is not initializing the KernelScope from the deployment component scope -------------------------------------------------------------------------------------------- Key: JBDEPLOY-69 URL: https://jira.jboss.org/jira/browse/JBDEPLOY-69 Project: JBoss Deployers Issue Type: Task Components: components Reporter: Adrian Brock Assignee: Adrian Brock Fix For: JBDEPLOY-2.0.0.CR1 When the BeanMetaDataDeployer creates the ControllerContext, it should initialise its scopes from the DeploymentUnit. -- 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

17 years, 11 months

2
3
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-335) Make the kernel build fail when tests don't pass

by Adrian Brock (JIRA)

Make the kernel build fail when tests don't pass ------------------------------------------------ Key: JBMICROCONT-335 URL: https://jira.jboss.org/jira/browse/JBMICROCONT-335 Project: JBoss MicroContainer Issue Type: Task Components: General Reporter: Adrian Brock Fix For: JBossMC.2.0.0.CR1 Since there are currently two failing tests in the kernel module, I've allowed the build to continue when there are test failures. The build should fail if the tests don't pass so the kernel/pom.xml needs changing back to <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-surefire-plugin</artifactId>  </plugin> once these tests have been fixed. -- 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

17 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-332) Logic error when checking controller context has no dependencies

by Adrian Brock (JIRA)

Logic error when checking controller context has no dependencies ---------------------------------------------------------------- Key: JBMICROCONT-332 URL: https://jira.jboss.org/jira/browse/JBMICROCONT-332 Project: JBoss MicroContainer Issue Type: Bug Components: Dependency Affects Versions: JBossMC.2.0.0.Beta16 Reporter: Adrian Brock Assignee: Adrian Brock Fix For: JBossMC.2.0.0.CR1 There is a logic error in AbstractController when a ControllerContext has no dependencies if (dependencies != null && dependencies.resolveDependencies(this, state)) result.add(ctx); Where result is the set of contexts that are eligible to advance to the next level. This should of course be: if (dependencies == null || dependencies.resolveDependencies(this, state)) result.add(ctx); Since a context with no dependencies can always advance to the next level. -- 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

17 years, 11 months

1
1
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 August 2008