February 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-1602) The order of RHS statements shouldn't affect behavior (insertLogical)

by Patrick Gras (JIRA)

The order of RHS statements shouldn't affect behavior (insertLogical) --------------------------------------------------------------------- Key: JBRULES-1602 URL: http://jira.jboss.com/jira/browse/JBRULES-1602 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Environment: Drools 4.0.7 & 4.0.4, Java5, eclipse compiler, windows XP. Reporter: Patrick Gras Assigned To: Mark Proctor I have a class 'Cat' that is dynamic (JavaBean with PropertyChangeSupport ) with only a 'name' attribute. Then I have the following rule: rule "test" when $cat:Cat( name == "tom" ) then $cat.setName("cat"); insertLogical(new String("test")); end When I test the rule against a Cat named tom, the logical inserted fact is not retracted. (So the fact is inserted because the rule matches, but is not retracted even if the rule is no more matching at the end.) If I change the order of the RHS, it works fine. The fact is inserted and then retracted. rule "test" when $cat:Cat( name == "tom" ) then insertLogical(new String("test")); $cat.setName("cat"); end So the behavior depends on the ordering of the RHS statements. Here is a complete example to show the problem: public class Cat { private String name; protected PropertyChangeSupport changes = new PropertyChangeSupport(this); public Cat(String name) { super(); this.name = name; } public String getName() { return this.name; } public void setName(String name) { final String oldName = this.name; this.name = name; this.changes.firePropertyChange("name", oldName, name); } public void addPropertyChangeListener(final PropertyChangeListener listener) { this.changes.addPropertyChangeListener(listener); } public void removePropertyChangeListener( final PropertyChangeListener listener) { this.changes.removePropertyChangeListener(listener); } } public class RHSOrderingTest { private static final String PACKAGE = "package ch.generali.pgr.rule "; private static final String IMPORT = "import ch.generali.pgr.rules.Cat "; private static final String WHEN = "rule \"test ok\" when $cat:Cat( name == \"tom\" ) "; private static final String THEN_OK = "then insertLogical(Integer.valueOf(1)); $cat.setName(\"cat\"); end"; private static final String THEN_KO = "then $cat.setName(\"cat\"); insertLogical(Integer.valueOf(1)); end"; private static final String RULE_OK = PACKAGE + IMPORT + WHEN + THEN_OK; private static final String RULE_KO = PACKAGE + IMPORT + WHEN + THEN_KO; private static final String QUERY = "query \"My test Integer\" integer : Integer( intValue == 1 ) end"; public static void main(String[] args) { boolean ok_1 = testWithRule(RULE_OK); boolean ok_2 = testWithRule(RULE_KO); System.out.println((ok_1 ? "SUCCESS: " : "FAILED: ") + THEN_OK); System.out.println((ok_2 ? "SUCCESS: " : "FAILED: ") + THEN_KO); } private static boolean testWithRule(String rule) { Cat tom = new Cat("tom"); RuleBase rb = createRuleBase(rule + "\n" + QUERY); WorkingMemory wm = rb.newStatefulSession(); wm.insert(tom, true); wm.fireAllRules(); QueryResults results = wm.getQueryResults("My test Integer"); return results.size() == 0; } private static RuleBase createRuleBase(String rules) { try { RuleBase ruleBase = RuleBaseFactory.newRuleBase(); PackageBuilderConfiguration conf = new PackageBuilderConfiguration(); PackageBuilder packageBuilder = new PackageBuilder(conf); Reader source = new StringReader(rules); packageBuilder.addPackageFromDrl(source); Package pkg = packageBuilder.getPackage(); ruleBase.addPackage(pkg); return ruleBase; } catch (Exception e) { throw new RuntimeException(e); } } } -- 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

14 years

7
24
0 / 0

[JBoss JIRA] Created: (JBRULES-1665) put offending rule name in exception messages

by Alex McCarrier (JIRA)

put offending rule name in exception messages --------------------------------------------- Key: JBRULES-1665 URL: http://jira.jboss.com/jira/browse/JBRULES-1665 Project: JBoss Drools Issue Type: Feature Request Components: Drl Parser/Builder Affects Versions: FUTURE Environment: all Reporter: Alex McCarrier Assigned To: Mark Proctor Priority: Minor It would be nice if drools compiler error messages would include the rule that caused the error. For instance, predicate eval errors, or "unable to resolve property" errors would state which rule was being evaluated when it encountered an error. Currently the developer has to go through the rules file looking for lines similar to the one reported in the error. Also, when it's this much work for a developer to find the offending rule, it is pretty much impossible for business users to figure out which rule they messed up. If it's at all possible to add the rule name to these error messages, please do so. It would make our lives a lot easier. :) -- 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

14 years, 1 month

2
1
0 / 0

[JBoss JIRA] Created: (JBRULES-680) Support real-time problem modification during solving with utils for the single thread subsystem

by Geoffrey De Smet (JIRA)

Support real-time problem modification during solving with utils for the single thread subsystem ------------------------------------------------------------------------------------------------ Key: JBRULES-680 URL: http://jira.jboss.com/jira/browse/JBRULES-680 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Solver Reporter: Geoffrey De Smet Assigned To: Geoffrey De Smet Rete/Drools is single threaded, and so is the current implementation of the localsearchsolver, but this single thread subsystem should be documented and utils should be provided to allow for real-time problem modification A simple way would be to use a producer-consumer pattern with a non blocking queue which holds "problem moves". Each step the problem moves could be used. Problems: - bestsolutionrecalled also needs it's score adjusted. so we'll need a 2th working memory: -- EITHER temporary, just for the problem move (or set of problem moves) -- EITHER all the time, but then we'd have to hold a chain of moves, some of which might not be doable at the end - cached selectors must be notified of refreshing their cache - solution cloning normally doesn't clone the problem facts, just the proposed solution references. Do we need a full clone now? -- 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

14 years, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (JBRULES-1801) drools-ant-4.0.7, DroolsCompilerAntTask, classloader mixup leads to ClassCastException if drools-compiler.jar part of classpathref

by Juergen none (JIRA)

drools-ant-4.0.7, DroolsCompilerAntTask, classloader mixup leads to ClassCastException if drools-compiler.jar part of classpathref ---------------------------------------------------------------------------------------------------------------------------------- Key: JBRULES-1801 URL: https://jira.jboss.org/jira/browse/JBRULES-1801 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-ant Affects Versions: 4.0.7 Reporter: Juergen none Assignee: Mark Proctor drools-4.0.7: Original error in build.xml: /home/juergen/workspace/eclipse/kusss-dev/build.xml:777: RuleBaseTask failed: Unable to load dialect 'org.drools.rule.builder.dialect.java.JavaDialectConfiguration:java' Traceback to: org.drools.compiler.PackageBuilderConfiguration, line 154+: Class cls = classLoader.loadClass( dialectClass ); DialectConfiguration dialectConf = (DialectConfiguration) cls.newInstance(); cls is org.drools.rule.builder.dialect.java.JavaDialectConfiguration, but loaded via classloader given in drools compile ant task property classpathref, while DialectConfiguration is loaded via ant tool classpath used for taskdef --> java.lang.ClassCastException: org.drools.rule.builder.dialect.java.JavaDialectConfiguration interim fix: make sure drools-compiler.jar is not in classpath of classloaderref suggested fix: Class cls = DialectConfiguration.class.getClassLoader().loadClass( dialectClass ); -- 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

14 years, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-1273) Create a maven2 plugin to allow rulebase compilation and serialization during a build (similar to the drools-ant task)

by Rainer Langbehn (JIRA)

Create a maven2 plugin to allow rulebase compilation and serialization during a build (similar to the drools-ant task) ---------------------------------------------------------------------------------------------------------------------- Key: JBRULES-1273 URL: http://jira.jboss.com/jira/browse/JBRULES-1273 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Rainer Langbehn Assigned To: Mark Proctor I already created the requested maven2 plugin and i would like to contribute it. -- 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

14 years, 1 month

7
26
0 / 0

[JBoss JIRA] Created: (JBRULES-677) Setup integration testing

by Geoffrey De Smet (JIRA)

Setup integration testing ------------------------- Key: JBRULES-677 URL: http://jira.jboss.com/jira/browse/JBRULES-677 Project: JBoss Rules Issue Type: Task Security Level: Public (Everyone can see) Components: Solver Reporter: Geoffrey De Smet Assigned To: Geoffrey De Smet Priority: Minor based on solver configs -- 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

14 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-1103) Tabu asperation based on stepscore

by Geoffrey De Smet (JIRA)

Tabu asperation based on stepscore ---------------------------------- Key: JBRULES-1103 URL: http://jira.jboss.com/jira/browse/JBRULES-1103 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Solver Reporter: Geoffrey De Smet Assigned To: Geoffrey De Smet Fix For: FUTURE Move tabu and property tabu could use "aspiration" Basically even if it's tabu, a move is accepted if the stepscore improves. For solution tabu this is pointless. Aspiration should occur on stepScore and NOT on decisionScore -- 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

14 years, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1617) Create a MC bean handle in the likes of java.ejb.Handle

by Carlo de Wolf (JIRA)

Create a MC bean handle in the likes of java.ejb.Handle ------------------------------------------------------- Key: EJBTHREE-1617 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1617 Project: EJB 3.0 Issue Type: Feature Request Components: common Reporter: Carlo de Wolf Assignee: Ales Justin Priority: Critical Fix For: 1.0.0-CR1 -- 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

14 years, 1 month

3
2
0 / 0

[JBoss JIRA] Created: (JBCLUSTER-153) EJB timer clustering and failover support

by Galder Zamarreno (JIRA)

EJB timer clustering and failover support ----------------------------------------- Key: JBCLUSTER-153 URL: http://jira.jboss.com/jira/browse/JBCLUSTER-153 Project: JBoss Clustering Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Galder Zamarreno Assigned To: Brian Stansberry Support for clustered EJB timer service providing failover -- 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

14 years, 1 month

6
7
0 / 0

[JBoss JIRA] Created: (JBRULES-1469) Add DecisionTable example for the TroubleTicket example

by Mark Proctor (JIRA)

Add DecisionTable example for the TroubleTicket example ------------------------------------------------------- Key: JBRULES-1469 URL: http://jira.jboss.com/jira/browse/JBRULES-1469 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Mark Proctor Assigned To: Mark Proctor Fix For: 5.0.0-M1 -- 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

14 years, 1 month

5
19
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 February 2009