May 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAOP-570) Ignore the ClassLoader on the JoinPointGenerator.generatedJoinPointClassCache

by Flavia Rainone (JIRA)

Ignore the ClassLoader on the JoinPointGenerator.generatedJoinPointClassCache ----------------------------------------------------------------------------- Key: JBAOP-570 URL: http://jira.jboss.com/jira/browse/JBAOP-570 Project: JBoss AOP Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 2.0.0.CR8 Reporter: Flavia Rainone Assigned To: Flavia Rainone Fix For: 2.0.0.CR9 This task consists in undoing what has been done for JBAOP-550. A bug in the class loader used by messaging tests took us to create JBAOP-550 unnecessarily (see the forum reference for more details) Taking the class loader into consideration for the cache is not necessary. The class loader will always be the same that loaded the instrumented class. -- 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, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-1521) ClassNotFound when deserializing rulebase

by Edson Tirelli (JIRA)

ClassNotFound when deserializing rulebase ----------------------------------------- Key: JBRULES-1521 URL: http://jira.jboss.com/jira/browse/JBRULES-1521 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: Drl Parser/Builder, Reteoo Affects Versions: 4.0.5 Reporter: Edson Tirelli Assigned To: Edson Tirelli Fix For: 4.0.6, 5.0.0-M1 Hi Group Members, In Drools 4.0.5 release most of the bugs with "Working Memory serialization" are fixed. But still the feature has few bugs. The bug scenario : 1. Create a rule Base & Working Memory (Stateful Session). 2. Assert some objects in Working Memory & call fireAll() 3. Serialize both Rule Base & Working Memory. 4. De Serialize Rule Base & Working Memory. 5. Remove Pkg/rule from Rule Base. 6. Serialize both Rule Base & Working Memory. 7. De Serialize Rule Base & Working Memory. ---------> In this step Working Memory De Serialization fails with java.lang.ClassNotFoundException. 8. Assert some more objects in Working Memory & call fireAll() I have tested the scenario using "MarshallingTest.java" from Drools Codebase. In the MarshallingTest.testSerializeAddRemove_NoClassDefFoundError() test case, I have appended bellow mentioned code snippet at end: ruleBase = (RuleBase) serializeIn( serializedRulebase ); session = ruleBase.newStatefulSession( new ByteArrayInputStream( serializedSession ) ); // throws java.lang.ClassNotFoundException Exception results = (List) session.getGlobal( "results" ); InternalFactHandle stilton5 = (InternalFactHandle) session.insert( new Cheese( "stilton", 30 ) ); InternalFactHandle brie5 = (InternalFactHandle) session.insert( new Cheese( "brie", 30 ) ); InternalFactHandle bob7 = (InternalFactHandle) session.insert( new Person( "bob", 30 ) ); InternalFactHandle bob8 = (InternalFactHandle) session.insert( new Person( "bob", 40 ) ); session.fireAllRules(); assertEquals( 8, results.size() ); assertEquals( bob7.getObject(), results.get( 6 ) ); assertEquals( bob8.getObject(), results.get( 7 ) ); serializedSession = null; serializedRulebase = null; serializedSession = serializeOut( session ); serializedRulebase = serializeOut( ruleBase ); session.dispose(); One more bug is: Can not serialize Working Memory if Rule contains Accumulate or Collect Conditional element. Because, both of them have nested static class "AccumulateMemory" & "CollectMemory" respectively, which are not serializable. We want to use Drools in our project with its "Working Memory serialization" feature to maintain state of Rule Engine between executions. So Fix of All bugs related to "Working Memory serialization" feature is very important for us. Thanks Siddhartha -- 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, 7 months

3
5
0 / 0

[JBoss JIRA] Created: (JBRULES-1594) Collect result pattern no constrained by bounded variables

by Ming Fang (JIRA)

Collect result pattern no constrained by bounded variables ---------------------------------------------------------- Key: JBRULES-1594 URL: http://jira.jboss.com/jira/browse/JBRULES-1594 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.0.0-M1 Reporter: Ming Fang Assigned To: Mark Proctor For a rule like this rule "example" when Integer(count:intValue) doubles: ArrayList(size == count) from collect(Double()) then System.out.println(doubles); end If I insert an Integer(2), I expect to have to insert 2 Doubles for the rule to fire. But this rule fires even with only one Double. However this rule behaves correctly. rule "example" when Integer(count:intValue) doubles: ArrayList(size == 2) from collect(Double()) then System.out.println(doubles); end -- 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, 7 months

3
5
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1923) Replace oswego by java.util.concurrent

by Julien Viet (JIRA)

Replace oswego by java.util.concurrent -------------------------------------- Key: JBPORTAL-1923 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1923 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Reporter: Julien Viet Assigned To: Julien Viet Fix For: Common-1.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

17 years, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1833) SetMap class does'nt properly use its Comparator field

by Sylvain FRANCOIS (JIRA)

SetMap class does'nt properly use its Comparator field ------------------------------------------------------ Key: JBPORTAL-1833 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1833 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Sylvain FRANCOIS org.jboss.portal.common.util.SetMap accepts a Comparator object in constructor, however map is never sorted with this Comparator. ListMap implementation is based on same design but sorts its content with its Comparator field. -- 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, 7 months

3
3
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1997) Couple of CMS Security issues

by Sohil Shah (JIRA)

Couple of CMS Security issues ----------------------------- Key: JBPORTAL-1997 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1997 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal CMS Affects Versions: 2.6.4 Final Reporter: Sohil Shah Assigned To: Sohil Shah Fix For: 2.6.5 Final The logic issue lies in the isPortletAccessible check in the CMSAdminPortlet. Side effects are: because of this check, the Portlet itself is unavailable even if the resources in the CMS are accessible as per the permissions set on the CMS. Behavior contradicts its setup usecases affected are: 1/ The CmsRootUser cannot access the CMS Admin tool. This completely defeats the purpose of the RootUser who should have all privileges to go in and fix things 2/ The CMSAdmin tool cannot be setup for access by Anonymous users -- 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, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAOP-568) Avoid extra info from being kept in the generated jp cache

by Flavia Rainone (JIRA)

Avoid extra info from being kept in the generated jp cache ---------------------------------------------------------- Key: JBAOP-568 URL: http://jira.jboss.com/jira/browse/JBAOP-568 Project: JBoss AOP Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 2.0.0.CR8 Reporter: Flavia Rainone Assigned To: Flavia Rainone Fix For: 2.0.0.CR9 GeneratedClassInfo, object used to keep the generated JoinPoint cache in JoinPointGenerator instances, keeps references to AdviceMethodProperties. However, the single information that is really required from AdviceMethodProperties during generated JoinPoint instantiation are the around cflow field names and initialization expressions. If we stop from keeping references to AdviceMethodProperties inside this cache, we will make it available for garbage collection. -- 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, 7 months

1
4
0 / 0

[JBoss JIRA] Created: (JBAOP-565) SuperClassesFirstWeavingStrategy instruments classes already loaded

by Flavia Rainone (JIRA)

SuperClassesFirstWeavingStrategy instruments classes already loaded ------------------------------------------------------------------- Key: JBAOP-565 URL: http://jira.jboss.com/jira/browse/JBAOP-565 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.0.0.CR8 Reporter: Flavia Rainone Assigned To: Flavia Rainone Fix For: 2.0.0.GA The method SuperClassesFirstWeavingStrategy tries to transform super classes that have already been loaded. As a result, on load time weaving we can see inconsistent transformations if there are aspects added/removed between two transformations of the same class. This bug can be seen when running the regression test jbaop484superproxyadvised.SuperClassIsAdvisedByProxyTestCase.testClassAdvisorAndNotInstanceAdvisor(): java.lang.RuntimeException: java.lang.NullPointerException at org.jboss.aop.proxy.container.GeneratedAOPProxyFactory.getProxy(GeneratedAOPProxyFactory.java:124) at org.jboss.aop.proxy.container.GeneratedAOPProxyFactory.createAdvisedProxy(GeneratedAOPProxyFactory.java:85) at org.jboss.test.aop.regression.jbaop484superproxyadvised.SuperClassIsAdvisedByProxyTestCase.createProxy(SuperClassIsAdvisedByProxyTestCase.java:196) at org.jboss.test.aop.regression.jbaop484superproxyadvised.SuperClassIsAdvisedByProxyTestCase.testClassAdvisorAndNotInstanceAdvisor(SuperClassIsAdvisedByProxyTestCase.java:137) Caused by: java.lang.NullPointerException at org.jboss.aop.proxy.container.ContainerProxyFactory.createProxyMethods(ContainerProxyFactory.java:631) at org.jboss.aop.proxy.container.ContainerProxyFactory.addMethodsAndMixins(ContainerProxyFactory.java:523) at org.jboss.aop.proxy.container.ContainerProxyFactory.createProxyCtClass(ContainerProxyFactory.java:215) at org.jboss.aop.proxy.container.ContainerProxyFactory.createProxyCtClass(ContainerProxyFactory.java:187) at org.jboss.aop.proxy.container.ContainerProxyFactory.generateProxy(ContainerProxyFactory.java:154) at org.jboss.aop.proxy.container.ContainerProxyFactory.getProxyClass(ContainerProxyFactory.java:144) at org.jboss.aop.proxy.container.ContainerProxyFactory.getProxyClass(ContainerProxyFactory.java:118) at org.jboss.aop.proxy.container.GeneratedAOPProxyFactory.generateProxy(GeneratedAOPProxyFactory.java:130) at org.jboss.aop.proxy.container.GeneratedAOPProxyFactory.getProxy(GeneratedAOPProxyFactory.java:116) ... 20 more -- 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, 7 months

2
5
0 / 0

[JBoss JIRA] Created: (JBAOP-558) Create a wiki page that document how to use aop with jdk1.4

by Stale Pedersen (JIRA)

Create a wiki page that document how to use aop with jdk1.4 ----------------------------------------------------------- Key: JBAOP-558 URL: http://jira.jboss.com/jira/browse/JBAOP-558 Project: JBoss AOP Issue Type: Sub-task Security Level: Public (Everyone can see) Affects Versions: 2.0.0.CR8 Reporter: Stale Pedersen Assigned To: Stale Pedersen Fix For: 2.0.0.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, 7 months

2
5
0 / 0

[JBoss JIRA] Created: (JBAOP-559) Remove references to JDK 1.4 from reference documentation and the tutorial examples

by Kabir Khan (JIRA)

Remove references to JDK 1.4 from reference documentation and the tutorial examples ----------------------------------------------------------------------------------- Key: JBAOP-559 URL: http://jira.jboss.com/jira/browse/JBAOP-559 Project: JBoss AOP Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Kabir Khan Assigned To: Stale Pedersen -- 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, 7 months

2
5
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira May 2008