July 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-949) the rules of decision table was looped.

by jiang jinfeng (JIRA)

the rules of decision table was looped. ----------------------------------------- Key: JBRULES-949 URL: http://jira.jboss.com/jira/browse/JBRULES-949 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Decision tables Affects Versions: 3.0.1 Environment: window xp, eclipse-3.1.2 Reporter: jiang jinfeng Assigned To: Mark Proctor There were some discussions about this issue in the drools-user mailing list already. In the decision table, salience = true: When I modify a variable in the action cell, even I have specified keyword "UNLOOP" to be true, all other rules satisfying the new conditions are fired (even for rules which already fired before). Therefore, the whole rule set is looped and can not stop running. Currently I need to set up a lot of flags to avoid this situation ... -- 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

19 years

2
1
0 / 0

[JBoss JIRA] Created: (JBRULES-502) Add binding semantics for decision table authors

by Scott Reed (JIRA)

Add binding semantics for decision table authors ------------------------------------------------ Key: JBRULES-502 URL: http://jira.jboss.com/jira/browse/JBRULES-502 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Decision tables Reporter: Scott Reed Assigned To: Mark Proctor The expressive capability of decision tables for non-programmer authors is limited. Especially, the author has no way to tell the developer to use the value of a property from one column in the condition for another. I can think of two ways that binding semantics could be added: Use the comment cells (i.e. "Age: Person's Age") - this is simple and expressive but would cause problems if an author wants to use the '<word>:' construct in a comment without intending it to be a binding. Add a designated row above or below the comment row. -- 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

19 years

2
1
0 / 0

[JBoss JIRA] Created: (JBRULES-906) Two or more function-definitions lead to "Function Compilation Error".

by Dr. Gernot Starke (JIRA)

Two or more function-definitions lead to "Function Compilation Error". ---------------------------------------------------------------------- Key: JBRULES-906 URL: http://jira.jboss.com/jira/browse/JBRULES-906 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Drl Parser/Builder Affects Versions: 3.1-m1 Environment: Mac OS X, regardless of JDK version Reporter: Dr. Gernot Starke Assigned To: Mark Proctor Two or more function-definitions lead to "function compilation error". Seems to be fixed in 4.0 M2... too bad I cannot currently upgrade. -- 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

19 years

3
2
0 / 0

[JBoss JIRA] Created: (JBRULES-451) Allow optional trailing comma "," for field constraint list

by Juergen none (JIRA)

Allow optional trailing comma "," for field constraint list ----------------------------------------------------------- Key: JBRULES-451 URL: http://jira.jboss.com/jira/browse/JBRULES-451 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Drl Parser/Builder Affects Versions: 3.0.4 Reporter: Juergen none Assigned To: Mark Proctor Priority: Optional With frequently re-arranging / adding / removing field constraints, I more than once forgot to add / remove trailing/separating commas in the field constraint list. would it be possible to extend the drools drl syntax to allow an optional trailing comma? e.g. A( a == 1, b == 2, // optional trailing comma, should not yield the syntax error ) A( a == 1, b == 2 // no (optional) trailing comma, like currently required, is also valid ) -- 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

19 years

2
1
0 / 0

[JBoss JIRA] Created: (JBRULES-969) To be able to access globals within functions

by Natraj Gudla (JIRA)

To be able to access globals within functions --------------------------------------------- Key: JBRULES-969 URL: http://jira.jboss.com/jira/browse/JBRULES-969 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: All Environment: Drools version 3.0.6, Using Eclipse IDE and simple DRL file working with Global variables Reporter: Natraj Gudla Assigned To: Mark Proctor Hello, I am using Drools 3.0.6. While using a global variable in a function, the compiler complains it cannot resolve the global variable name. Something like below global com.sample.ExampleLogger customLogger; function void logMessage(String msg){ customLogger.logMessage("Log Message from the function"); } In the above code, it complains "customLogger cannot be resolved". I am able to refer the global in the consequence of a rule directly. What is the problem using the reference within a function. On the other hand, i am able to do something like function void logMessage(ExampleLogger custLogger,String msg){ custLogger.logMessage(msg+" Accept gloabal as function parameter"); } and call from the consequence of a rule : logMessage(customLogger); // I am passing the global to the function as an argument and then use it to log a message. This way is working. But not the first way of using the global in the function. It would be a good feature to have the globals accessible within functions. -- 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

19 years

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-754) For each added package coming from a DRL , ALL previously loaded rules are compiled again

by Marcos Tengelmann (JIRA)

For each added package coming from a DRL , ALL previously loaded rules are compiled again ----------------------------------------------------------------------------------------- Key: JBRULES-754 URL: http://jira.jboss.com/jira/browse/JBRULES-754 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 3.0.5 Environment: Any OS. Reporter: Marcos Tengelmann Assigned To: Mark Proctor For each file we add to rule base using addPackageFromDRL, all previously added rules are compiled again. If we use the same pacjage builder the problem(? Is it a problem or a expected behavior?) reported happens. If we use a different packageBuilder for each file, it does not happen. -- 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

19 years

3
2
0 / 0

[JBoss JIRA] Created: (JBRULES-938) Conditions with multiple parameters aren't always correctly parsed in decision tables

by Fabien Lafarge (JIRA)

Conditions with multiple parameters aren't always correctly parsed in decision tables ------------------------------------------------------------------------------------- Key: JBRULES-938 URL: http://jira.jboss.com/jira/browse/JBRULES-938 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Decision tables Affects Versions: 4.0.0.MR2, 3.0.6 Reporter: Fabien Lafarge Assigned To: Mark Proctor When the first parameter ($1) is present at the beginning of a condition (example rule: "$1! = $2"), SpreadsheetCompiler will not replace parameters with their values in SnippetBuilder.build(...), shouldn't if ( this._template.indexOf( SnippetBuilder.PARAM_PREFIX + "1" ) == 0 ) { be replaced with if ( this._template.indexOf( SnippetBuilder.PARAM_PREFIX + "1" ) >= 0 ) { ? -- 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

19 years

3
3
0 / 0

[JBoss JIRA] Closed: (JBRULES-219) JRules style temporal rules

by Mark Proctor (JIRA)

[ http://jira.jboss.com/jira/browse/JBRULES-219?page=all ] Mark Proctor closed JBRULES-219. -------------------------------- Resolution: Out of Date > JRules style temporal rules > --------------------------- > > Key: JBRULES-219 > URL: http://jira.jboss.com/jira/browse/JBRULES-219 > Project: JBoss Rules > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Reteoo > Reporter: Mark Proctor > Assigned To: Mark Proctor > > There is a public paper on JRules temporal rules, which is event based and more flexible than our current system. We should look into adding this. -- 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

19 years

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-747) Conversion of rules from DRL to XML format using "from" - CE

by Kioumars Namiri (JIRA)

Conversion of rules from DRL to XML format using "from" - CE ------------------------------------------------------------- Key: JBRULES-747 URL: http://jira.jboss.com/jira/browse/JBRULES-747 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: xml Affects Versions: 3.1-m1 Environment: Windows XP, Eclipse 3.2, JBoss Rules 3.1M1 Reporter: Kioumars Namiri Assigned To: Mark Proctor The conversion of "from"-Conditional Element from DRL format to XML is not supported. XMLDumper reports Error while converting the drl file: no visitor implementation for : class org.drools.lang.descr.FromDescr : org.drools.lang.descr.FromDescr See http://article.gmane.org/gmane.comp.java.drools.user/6709 -- 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

19 years

3
2
0 / 0

[JBoss JIRA] Created: (JBRULES-508) Improve error reporting: When adding a compiled package to a rulebase, the compiled package may have still errors

by Michael Neale (JIRA)

Improve error reporting: When adding a compiled package to a rulebase, the compiled package may have still errors ----------------------------------------------------------------------------------------------------------------- Key: JBRULES-508 URL: http://jira.jboss.com/jira/browse/JBRULES-508 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Drl Parser/Builder Affects Versions: 3.0.3 Reporter: Michael Neale Assigned To: Mark Proctor When adding a compiled package to a rulebase, the compiled package may have still errors - at the moment this is caught and an exception thrown. This is fine, as the errors are accumulated in PackageBuilder. But, given that people ignore the message, may be better to keep the error list in the compiled package, and in the thrown error, pretty print the error message as part of the exception so it looks nicer for newbies. -- 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

19 years

2
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 July 2007