March 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-553) Add newlines in parser error messages

by Dirk Bergstrom (JIRA)

Add newlines in parser error messages ------------------------------------- Key: JBRULES-553 URL: http://jira.jboss.com/jira/browse/JBRULES-553 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 3.0.4 Reporter: Dirk Bergstrom Assigned To: Mark Proctor Priority: Minor Some kinds of parser errors get strung together on a single very long line, which makes it irritating to debug problems. This doozy is 332 characters long: org.drools.rule.InvalidRulePackage: Rule Compilation error Class "net.juniper.dash.RUM" has no method named "countPicklistFieldsComparingxTo" Instance method "countPicklistFieldsComparingxTo" cannot be invoked in static context Exception:2 errors while compiling unit "net/juniper/dash/Rule_RLIs_with_missing_func_specs_0.java" That's a lot of side-scrolling to figure out what happened. Breaking it up into four or five lines would greatly increase readability. -- 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, 10 months

3
2
0 / 0

[JBoss JIRA] Created: (JBRULES-501) DRL -> decision table (round trip)

by Scott Reed (JIRA)

DRL -> decision table (round trip) ---------------------------------- Key: JBRULES-501 URL: http://jira.jboss.com/jira/browse/JBRULES-501 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Decision tables Reporter: Scott Reed Assigned To: Mark Proctor It would be extremely useful to be able to convert existing rules to decision tables. The educational value alone would make it worth while, but it would speed up development as well since the DRL -> decision table mapping is not straight forward and cell merging and coloring is fairly tedious. Users would probably want to be able to select the rules and functions to be mapped. If so, then the results of the mapping would have to be one or more decision table files and a new DRL file containing the rules and functions that were not converted. -- 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, 10 months

3
4
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

18 years, 10 months

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

18 years, 10 months

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

18 years, 10 months

3
2
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

18 years, 10 months

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

18 years, 10 months

2
1
0 / 0

[JBoss JIRA] Created: (JBRULES-522) update maven repo

by Michael Neale (JIRA)

update maven repo ----------------- Key: JBRULES-522 URL: http://jira.jboss.com/jira/browse/JBRULES-522 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 3.0.4 Reporter: Michael Neale Assigned To: Mark Proctor Is it easy to update the jboss repo? (easier then the maven one) as we have direct access? What about generating the maven poms etc - hows that work? -- 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, 10 months

3
2
0 / 0

[JBoss JIRA] Created: (JBRULES-427) Language Level Default to Java Specification

by Geoffrey Wiseman (JIRA)

Language Level Default to Java Specification -------------------------------------------- Key: JBRULES-427 URL: http://jira.jboss.com/jira/browse/JBRULES-427 Project: JBoss Rules Issue Type: Patch Security Level: Public (Everyone can see) Components: Drl Parser/Builder Reporter: Geoffrey Wiseman Assigned To: Mark Proctor Attachments: drools-compiler-languageLevel.txt See the attached patch for drools-compiler that sets the language level to the same one as the runtime environment, if it's viable. Can still be overridden in code or with a system property. -- 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, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (JBRULES-377) the whole rule set was looped.

by wen Lin (JIRA)

the whole rule set was looped. ------------------------------ Key: JBRULES-377 URL: http://jira.jboss.com/jira/browse/JBRULES-377 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: wen Lin 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

18 years, 10 months

3
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 March 2007