April 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMICROCONT-281) Allow anonymous beans

by Ales Justin (JIRA)

Allow anonymous beans --------------------- Key: JBMICROCONT-281 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-281 Project: JBoss MicroContainer Issue Type: Feature Request Components: Kernel Affects Versions: JBossMC-2.0.0.Beta12 Reporter: Ales Justin Assigned To: Ales Justin Fix For: JBossMC.2.0.0.CR1 Allow for beans to be installed w/o defining the name, e.g. let MC create some GUID/unique name. This is specially useful for inner beans. -- 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

18 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-4088) Background validation seconds

by Adrian Brock (JIRA)

Background validation seconds ----------------------------- Key: JBAS-4088 URL: http://jira.jboss.com/jira/browse/JBAS-4088 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JCA service Affects Versions: JBossAS-5.0.0.Beta1 Reporter: Adrian Brock Assigned To: Weston Price Support background-validation-seconds and deprecate background-validation-minutes Unlike the idle timeout, the background validation needs to be more finegrained. -- 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

18 years, 1 month

3
9
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1979) When hot-redelpoying a portlet, render parameters should be deleted

by Thomas Heute (JIRA)

When hot-redelpoying a portlet, render parameters should be deleted ------------------------------------------------------------------- Key: JBPORTAL-1979 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1979 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal Core Affects Versions: 2.6.4 Final Reporter: Thomas Heute Assigned To: Thomas Heute When a portlet is hot-redeployed, portlet session parameters are deleted (portlet session is destroyed) but render parameters are not (portal session is still running). It may lead to some inconsistent state of the portlet and unexpected behavior while in development. -- 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

18 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1976) WorkflowSoftDependency is not working correclty anymore

by Thomas Heute (JIRA)

WorkflowSoftDependency is not working correclty anymore ------------------------------------------------------- Key: JBPORTAL-1976 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1976 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Core Affects Versions: 2.6.4 Final Reporter: Thomas Heute Assigned To: Thomas Heute Fix For: 2.7 Final, 2.6.5 Final The identity service tried to deploy the BP definition before the workflow service is started. -- 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

18 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBDEPLOY-30) Improve reporting of circular dependency errors

by Scott M Stark (JIRA)

Improve reporting of circular dependency errors ----------------------------------------------- Key: JBDEPLOY-30 URL: http://jira.jboss.com/jira/browse/JBDEPLOY-30 Project: JBoss Deployers Issue Type: Feature Request Affects Versions: JBDEPLOY-2.0.0.Beta12 Reporter: Scott M Stark Fix For: JBDEPLOY-2.0.0.CR1 -- 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

18 years, 1 month

3
3
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-279) Check for InstanceAnnotation when doing hasMetaDataAtInstanceLevel in AOPConstructorJoinpoint

by Ales Justin (JIRA)

Check for InstanceAnnotation when doing hasMetaDataAtInstanceLevel in AOPConstructorJoinpoint --------------------------------------------------------------------------------------------- Key: JBMICROCONT-279 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-279 Project: JBoss MicroContainer Issue Type: Feature Request Components: AOP Affects Versions: JBossMC-2.0.0.Beta12 Reporter: Ales Justin Assigned To: Ales Justin Fix For: JBossMC.2.0.0.CR1 When AOP asks whether there are instance annotations it does this to decide whether an instance proxy is required. In some cases, e.g. the @JMX annotation, the instance annotation does not require an instance proxy instead we are just reusing the point cut language to invoke "advices" during deployment. To better handle this case, we should be able to meta annotate an annotation as not requiring an instance proxy, e.g. something like: @org.jboss.metadata.spi.annotation.InstanceAnnotation(false) public @interface JMX { ... } then we can tell aop whether an instance proxy is required. -- 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

18 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBAOP-550) Generated JoinPoint class cache ignores class loader

by Flavia Rainone (JIRA)

Generated JoinPoint class cache ignores class loader ---------------------------------------------------- Key: JBAOP-550 URL: http://jira.jboss.com/jira/browse/JBAOP-550 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.0.0.CR8 Reporter: Flavia Rainone Fix For: 2.0.0.GA The cache contained in JoinPointGenerator stores the generated classes without taking into account the class loader. If a class name retrieved from this cache is used to load the class in a different class loader, a ClassNotFound error will occur. -- 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

18 years, 1 month

1
4
0 / 0

[JBoss JIRA] Created: (JBCACHE-1326) TxInterceptor leaks MethodCall to thread

by Brian Stansberry (JIRA)

TxInterceptor leaks MethodCall to thread ---------------------------------------- Key: JBCACHE-1326 URL: http://jira.jboss.com/jira/browse/JBCACHE-1326 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: Transactions Affects Versions: 2.1.0.GA Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: 2.1.1.GA, 2.2.0.GA The various Synchronization callbacks in TxInterceptor end up calling the equivalent of cache.getInvocationContext().setMethodCall(xxx) but then don't restore the InvocationContext to its previous state when done. All other calls to InvocationContext.setMethodCall() do reverse themselves after the call is executed, so the effect is whatever MethodCall a TxInterceptor synchronization last associated to a thread ends up staying with that thread until some random other synchronization changes it to something different. This is showing up in the AS as a classloader leak, since the leaked MethodCall has a ref to undeployed classes. If a server had a large thread pool, the leak could be long lasting. I've added an assertion to org.jboss.cache.invocationcontext.TransactionTest.doScrubbingTest that shows 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

18 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-5372) Move XACML Tests from AS5/Trunk to security-xacml/trunk/jboss-sunxacml

by Anil Saldhana (JIRA)

Move XACML Tests from AS5/Trunk to security-xacml/trunk/jboss-sunxacml ---------------------------------------------------------------------- Key: JBAS-5372 URL: http://jira.jboss.com/jira/browse/JBAS-5372 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Test Suite Affects Versions: JBossAS-5.0.0.Beta4 Reporter: Anil Saldhana Assigned To: Marcus Moyses Priority: Minor Fix For: JBossAS-5.0.0.CR1 I had done xacml tests long long ago (maybe a year ago) in the AS5 test suite. The location is: http://anonsvn.jboss.org/repos/jbossas/trunk/testsuite/src/main/org/jboss... The test resources are under: http://anonsvn.jboss.org/repos/jbossas/trunk/testsuite/src/resources/secu... Please move these tests into the jboss-sunxacml project under src/tests/java and src/tests/resources Ensure that the AS5 testsuite compiles fine. You can try the following. $> ant tests-security-basic-unit -- 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

18 years, 1 month

2
1
0 / 0

[JBoss JIRA] Created: (JBBUILD-465) Automatically download source jars if they exist.

by Paul Gier (JIRA)

Automatically download source jars if they exist. ------------------------------------------------- Key: JBBUILD-465 URL: http://jira.jboss.com/jira/browse/JBBUILD-465 Project: JBoss Build System Issue Type: Feature Request Components: maven-buildmagic-thirdparty-plugin Reporter: Paul Gier Fix For: maven-buildmagic-thirdparty-plugin-2.0 If source jars are available in the maven repository, the buildmagic-thirdparty plugin should automatically download them. -- 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

18 years, 1 month

1
2
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 April 2008