October 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-966) update(fact) in 2 rules dont check for other updated facts - a loop is created

by Felipe Piccolini (JIRA)

update(fact) in 2 rules dont check for other updated facts - a loop is created ------------------------------------------------------------------------------ Key: JBRULES-966 URL: http://jira.jboss.com/jira/browse/JBRULES-966 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Reteoo Affects Versions: 4.0.0.MR3 Environment: tested on eclipse 3.2, JBossRules 4.0MR3, OS Mac OSX 10.4.10 Reporter: Felipe Piccolini Assigned To: Mark Proctor When using update in 2 rules that update the same object... a loop is created even when trying to avoid the loop adding an extra condition to each rule inserting an ArrayList as a fact too, so each rule should not be evaluated again... //-------RULES----------------------------- package org.drools.test #list any import classes here. import java.util.List import java.util.ArrayList import cl.bluesoft.test.rules.Fact #declare any global variables here rule "test update A" salience 699 no-loop when $f : Fact($n: number > 0) $list: ArrayList( this excludes "key1") then System.out.println("A-fact number1:"+$f.getNumber()+" list 1:"+$list); $list.add("key1"); $f.setNumber($n + 1); update ($f); update ($list); System.out.println("A-fact number2:"+$f.getNumber()+" list 2:"+$list); end rule "test update B" salience 699 no-loop when $f : Fact($n: number > 1) $list: ArrayList( this excludes "key2") then System.out.println("B-fact number1:"+$f.getNumber()+" list 1:"+$list); $list.add("key2"); $f.setNumber($n + 1); update ($f); update ($list); System.out.println("B-fact number2:"+$f.getNumber()+" list 2:"+$list); end //-------FACT----------------------------- public class Fact implements Serializable { private static final long serialVersionUID = 331627137981862975L; private int number; public Fact(int number){ this.number = number; } public Fact(){ this(0); } /** * @return the number */ public int getNumber() { return number; } /** * @param number the number to set */ public void setNumber(int number) { this.number = number; } } //------TEST--------- public class TestUpdateFact implements Serializable { private static final long serialVersionUID = -574789596641083743L; /** * @param args */ public static void main(String[] args) { RuleBase ruleBase = RuleBaseFactory.newRuleBase(); Package pkg = builder.getPackage(); .... WorkingMemory session = ruleBase.getStatefulSession(); ...etc etc... List list = new ArrayList(); Fact fact1 = new Fact(1); session.insert(fact1 false); session.insert(list, false); session.fireAllRules(); session.dispose(); } } //--------OUTPUT------------ A-fact number1:1 list 1:[] A-fact number2:2 list 2:[key1] B-fact number1:2 list 1:[key1] B-fact number2:3 list 2:[key1, key2] A-fact number1:3 list 1:[key1, key2] A-fact number2:4 list 2:[key1, key2, key1] B-fact number1:4 list 1:[key1, key2, key1] B-fact number2:5 list 2:[key1, key2, key1, key2] A-fact number1:5 list 1:[key1, key2, key1, key2] A-fact number2:6 list 2:[key1, key2, key1, key2, key1] B-fact number1:6 list 1:[key1, key2, key1, key2, key1] B-fact number2:7 list 2:[key1, key2, key1, key2, key1, key2] A-fact number1:7 list 1:[key1, key2, key1, key2, key1, key2] A-fact number2:8 list 2:[key1, key2, key1, key2, key1, key2, key1] B-fact number1:8 list 1:[key1, key2, key1, key2, key1, key2, key1] .... for ever..... So a loop is created... only when I use update and both rules... condition about the list not containing "key1" and "key2" seems not properly chequed... -- 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, 2 months

3
4
0 / 0

[JBoss JIRA] Created: (JBAS-3858) Update tc6-cluster.aop to match the current configuration

by Brian Stansberry (JIRA)

Update tc6-cluster.aop to match the current configuration --------------------------------------------------------- Key: JBAS-3858 URL: http://jira.jboss.com/jira/browse/JBAS-3858 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Ben Wang Fix For: JBossAS-5.0.0.Beta1 The pojocache-aop.xml used in JBC 2.0 is quite different from what we have in tc6-cluster.aop. We need to sync up. We want to maintain support for the old Tomcat-specific interface markers as well. -- 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, 2 months

6
12
0 / 0

[JBoss JIRA] Created: (SECURITY-88) Refactor JaasSecurityManager into JBossAuthenticationManager

by Anil Saldhana (JIRA)

Refactor JaasSecurityManager into JBossAuthenticationManager ------------------------------------------------------------ Key: SECURITY-88 URL: http://jira.jboss.com/jira/browse/SECURITY-88 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.0.1.GA Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0.2.GA The code that exists in JaasSecurityManager needs to be pulled into a generic delegate in JBossSX such that the JaasSecurityManager in the AS security integration as well as the default AuthenticationManager can reuse. -- 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, 2 months

1
4
0 / 0

[JBoss JIRA] Created: (SECURITY-50) XACML EJB Layer: Role Reference Checks

by Anil Saldhana (JIRA)

XACML EJB Layer: Role Reference Checks -------------------------------------- Key: SECURITY-50 URL: http://jira.jboss.com/jira/browse/SECURITY-50 Project: JBoss Security and Identity Management Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JBossSX Affects Versions: 2.0.0.BETA Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0.1 Provide a mechanism to do EJBContext.isCallerInRole checks when xacml is enabled. -- 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, 2 months

1
3
0 / 0

[JBoss JIRA] Created: (SECURITY-29) Validate Jacc Policy Module handles all run-as scenarios

by Anil Saldhana (JIRA)

Validate Jacc Policy Module handles all run-as scenarios -------------------------------------------------------- Key: SECURITY-29 URL: http://jira.jboss.com/jira/browse/SECURITY-29 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Components: JBossSX Affects Versions: 2.0.0.BETA Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0 With the roles being added to the security context via the mapping framework (for example), there may be cases where in run-as scenarios may not be adequately tested with the new Jacc authorization stuff. -- 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, 2 months

1
3
0 / 0

[JBoss JIRA] Created: (SECURITY-27) Container Task:JBoss 4.2.x related Tasks for Security 2.0

by Anil Saldhana (JIRA)

Container Task:JBoss 4.2.x related Tasks for Security 2.0 --------------------------------------------------------- Key: SECURITY-27 URL: http://jira.jboss.com/jira/browse/SECURITY-27 Project: JBoss Security Issue Type: Task Security Level: Public (Everyone can see) Components: JBossSX Affects Versions: 2.0 Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0 Container task for all 4.2.x related tasks that need to be performed for the 5.x releases of JBAS. -- 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, 2 months

1
4
0 / 0

[JBoss JIRA] Created: (SECURITY-28) JACC: <role-name>*</role-name> in web.xml should allow configurable authorization bypass

by Anil Saldhana (JIRA)

JACC: <role-name>*</role-name> in web.xml should allow configurable authorization bypass ---------------------------------------------------------------------------------------- Key: SECURITY-28 URL: http://jira.jboss.com/jira/browse/SECURITY-28 Project: JBoss Security Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.0 Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0 JBAS-1824 -- 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, 2 months

1
5
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1459) portal:service=TreeCache,type=hibernate should define ClusterConfig

by Galder Zamarreno (JIRA)

portal:service=TreeCache,type=hibernate should define ClusterConfig ------------------------------------------------------------------- Key: JBPORTAL-1459 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1459 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.6.CR1, 2.6.CR2, 2.4.1 SP1, 2.4.1 Final Reporter: Galder Zamarreno portal:service=TreeCache,type=hibernate omits ClusterConfig which can lead to confusion when trying to separate different AS + Portal clusters. Here's, bearing in mind the status of the JBC/HB integration, a good starting point: <attribute name="ClusterConfig"> <config> <UDP mcast_addr="${portal.hibernate.cache.udpGroup:224.0.0.36}" mcast_port="${portal.hibernate.cache.udpPort:55566}" ip_ttl="8" ip_mcast="true" mcast_send_buf_size="150000" mcast_recv_buf_size="80000" ucast_send_buf_size="150000" ucast_recv_buf_size="80000" loopback="false" up_thread="false" down_thread="false" /> <PING timeout="2000" num_initial_members="3" up_thread="false" down_thread="false" /> <MERGE2 min_interval="10000" max_interval="20000" up_thread="false" down_thread="false" /> <FD_SOCK up_thread="false" down_thread="false" /> <FD shun="true" timeout="20000" max_tries="5" up_thread="false" down_thread="false" /> <VERIFY_SUSPECT timeout="1500" up_thread="false" down_thread="false"/> <pbcast.NAKACK gc_lag="50" retransmit_timeout="600,1200,2400,4800" max_xmit_size="8192" discard_delivered_msgs="true" up_thread="false" down_thread="false"/> <UNICAST timeout="600,1200,2400" window_size="100" min_threshold="10" up_thread="false" down_thread="false"/> <pbcast.STABLE desired_avg_gossip="20000" up_thread="false" down_thread="false"/> <pbcast.GMS join_timeout="5000" join_retry_timeout="2000" shun="true" print_local_addr="true" up_thread="false" down_thread="false"/> <FRAG2 frag_size="8192" up_thread="false" down_thread="false"/> <pbcast.STATE_TRANSFER up_thread="false" down_thread="false"/> </config> </attribute> It'd be interesting to change the ClusterName as well: <attribute name="ClusterName">${portal.hibernate.cache.partition.name:portal.hibernate}</attribute> This configuration works and should be much better than the default one provided by JBossCache. -- 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, 2 months

4
4
0 / 0

[JBoss JIRA] Created: (SECURITY-61) Use JBossSubject rather than JAAS Subject

by Anil Saldhana (JIRA)

Use JBossSubject rather than JAAS Subject ----------------------------------------- Key: SECURITY-61 URL: http://jira.jboss.com/jira/browse/SECURITY-61 Project: JBoss Security and Identity Management Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JBossSX, Security SPI Affects Versions: 2.0.GA Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0.1 The JAAS Subject is quite inflexible. There is a need for a customized Subject. Let us call it JBossSubject which can internally hold a Jaas Subject. -- 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, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (SECURITY-46) SASL Implementation

by Anil Saldhana (JIRA)

SASL Implementation --------------------- Key: SECURITY-46 URL: http://jira.jboss.com/jira/browse/SECURITY-46 Project: JBoss Security and Identity Management Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JBossSX, JEMS Integration Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0.1 Need to get an implementation of SASL for client/server kind of setup for JBoss AS. This will work off of the Security Client implementation and then security managers on the server side. -- 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, 2 months

1
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2007