May 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-980) Support drl files that contain only one rule

by Kris Verlaenen (JIRA)

Support drl files that contain only one rule -------------------------------------------- Key: JBRULES-980 URL: http://jira.jboss.com/jira/browse/JBRULES-980 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Eclipse IDE Reporter: Kris Verlaenen Assigned To: Kris Verlaenen Fix For: FUTURE As possible in the BRMS, a drl file can possibly contain only one rule without rule name, in combination with a .package file. Currently, the drl editor does not support this type of drl file. -- 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

13 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-804) Provide "Source Path" with includes/excludes pattern capability for JBoss Rules Eclipse IDE (3.1-M1 currently validates _all_ .xls files in project)

by Bree VanOss (JIRA)

Provide "Source Path" with includes/excludes pattern capability for JBoss Rules Eclipse IDE (3.1-M1 currently validates _all_ .xls files in project) ---------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBRULES-804 URL: http://jira.jboss.com/jira/browse/JBRULES-804 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Eclipse IDE Affects Versions: 3.1-m1 Environment: WinXP, Sun JRE 1.4.2_12 Reporter: Bree VanOss Assigned To: Mark Proctor Priority: Minor The Eclipse "Drools Builder" is validating every Excel (.xls) in my rules project. Apparently this feature was added to 3.1-M1 by Kris. I really like the idea of validating decision tables in Eclipse, my issue is that we have FIT tests (in Excel) in a separate source folder in our "rules project". These .xls files are falsely being identified as decision tables with a ton of problems. Validation also seems to take much longer than it does with the 3.0.x branch (like from 30 seconds in 3.0 to to 5 minutes in 3.1 !?!?). Though the two issues may be related. A common way of dealing with this problem in Eclipse is to allow for ant-like "source path include/exclude" patterns. i.e. exclude test/**/*.xls For that matter it would be nice to have the same thing for standard DRL files. The validation of a large rule base can take some time and randomly results in exceptions much of the time. Once I've tested and verified a set of rules I could (optionally) exclude them from validation. -- 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

13 years, 9 months

5
5
0 / 0

[JBoss JIRA] Created: (JBRULES-1213) Context assist in .drl when different to then

by ekkehard gentz (JIRA)

Context assist in .drl when different to then --------------------------------------------- Key: JBRULES-1213 URL: http://jira.jboss.com/jira/browse/JBRULES-1213 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Eclipse IDE Affects Versions: 4.0.1 Environment: Drools 4.0.1, Eclipse 3.3, OSX 10.4.10 Reporter: ekkehard gentz Assigned To: Mark Proctor Fix For: 4.0.2 context assist in .drl editor has different behaviour in "when" section compared to "then" using drools examples StateExampleUsingSalience.drl when ... State. only shows (), null doing the same in then... State. shows class, this, FINISHED, NOT_RUN because in many cases tests in the LHS are against constants it would be good to show them -- 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

13 years, 9 months

3
2
0 / 0

[JBoss JIRA] Created: (JBRULES-1209) Extend RulesView sorting

by ekkehard gentz (JIRA)

Extend RulesView sorting ------------------------ Key: JBRULES-1209 URL: http://jira.jboss.com/jira/browse/JBRULES-1209 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Eclipse IDE Affects Versions: 4.0.2 Reporter: ekkehard gentz Assigned To: Mark Proctor Priority: Minor Being able to get an overview of all current ruleflow-groups and the rules they contain would be very helpful. would be nice to extend the RulesView so that it supports sorting not only based on package but for example also on ruleflow-group. -- 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

13 years, 9 months

3
3
0 / 0

[JBoss JIRA] Created: (JBRULES-1960) Syntaxcoloring wrong if DSL contains a "#"-Character

by Norbert Ziegler (JIRA)

Syntaxcoloring wrong if DSL contains a "#"-Character ---------------------------------------------------- Key: JBRULES-1960 URL: https://jira.jboss.org/jira/browse/JBRULES-1960 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-eclipse Affects Versions: 5.0.0.M5 Environment: eclipse 3.4, WinXP, jre6u10 Reporter: Norbert Ziegler Assignee: Mark Proctor Priority: Minor While editing a DSL-File one can see that everything after an #-Character is colored as comment, regardless of the position of the #. Indeed, it is not a comment. Imagine the following line in a DSL: Compute noselength to #MYVAR * #AGE then everything at / after "#MYVAR" is rendered as a comment. In this case a comment should only be recognized if the first non-empty-char of the line is the "#" -- 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

13 years, 9 months

3
4
0 / 0

[JBoss JIRA] Created: (JBRULES-1404) Introducing "eval(), from, collect, accumulate" support in the Guided Rule Editor

by Massimiliano Magistri (JIRA)

Introducing "eval(), from, collect, accumulate" support in the Guided Rule Editor --------------------------------------------------------------------------------- Key: JBRULES-1404 URL: http://jira.jboss.com/jira/browse/JBRULES-1404 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Eclipse IDE Affects Versions: 4.0.3 Environment: Eclipse Europa 3.3.1.1 Reporter: Massimiliano Magistri I would like to introduce an "eval()" expression when I use The Guided Rule Editor. I'd like to introduce statements like "from, collect, accumulate" as well. Thank You. -- 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

13 years, 9 months

3
3
0 / 0

[JBoss JIRA] Created: (JBRULES-2062) WorkingMemoryView in eclipse debugger does not show facts in entry points

by Edson Tirelli (JIRA)

WorkingMemoryView in eclipse debugger does not show facts in entry points ------------------------------------------------------------------------- Key: JBRULES-2062 URL: https://jira.jboss.org/jira/browse/JBRULES-2062 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-eclipse Affects Versions: 5.0.0.CR1 Reporter: Edson Tirelli Assignee: Kris Verlaenen The engine has separate object stores for each entry point. The current implementation only shows facts in the main entry point (working memory). Needs to be updated to show facts in each of the entry points. -- 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

13 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-1990) Drools workbench should ignore files in derived folders

by Benjamin Papez (JIRA)

Drools workbench should ignore files in derived folders ------------------------------------------------------- Key: JBRULES-1990 URL: https://jira.jboss.org/jira/browse/JBRULES-1990 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-eclipse Affects Versions: 4.0.7 Reporter: Benjamin Papez Assignee: Mark Proctor In my Eclipse projects (based on maven) I am tagging the target folder as Derived (via right mouse click on folder -> Properties). Eclipse is then not running the validators on that folder, but Drools does. So all the errors are reported twice. Please ignore the copies in Derived folders when doing validation. -- 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

13 years, 9 months

3
3
0 / 0

[JBoss JIRA] Created: (JBRULES-1972) Show DRL for decision tables

by Simon Spielmann (JIRA)

Show DRL for decision tables ---------------------------- Key: JBRULES-1972 URL: https://jira.jboss.org/jira/browse/JBRULES-1972 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-eclipse Reporter: Simon Spielmann Assignee: Mark Proctor Sometimes it is very useful to see the generated drl for a decision table. Without it you can't even set breakpoints. I suggest to add a menu item e.g. "show drl" to the context menu for a spreadsheet file in the eclipse ide. I think this shouldn't be to hard to implement. -- 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

13 years, 9 months

3
3
0 / 0

[JBoss JIRA] Created: (JBRULES-1968) Eclipse ruleflow editor cut, copy and paste operations appear to be allowed but do not work

by Shahad Ahmed (JIRA)

Eclipse ruleflow editor cut, copy and paste operations appear to be allowed but do not work ------------------------------------------------------------------------------------------- Key: JBRULES-1968 URL: https://jira.jboss.org/jira/browse/JBRULES-1968 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-eclipse, drools-eclipse (expert), drools-eclipse (flow) Affects Versions: 5.0.0.M5 Reporter: Shahad Ahmed Assignee: Mark Proctor The Edit menu in the drools eclipse plugin contains options to Cut, Copy and Paste nodes for a ruleflow editor. However, these operations do not work in the editor and cause exceptions to be reported in the eclipse log. For example, if you attempt to copy a ruleflow node then you get the following error on the eclipse log: !ENTRY org.eclipse.ui 4 4 2009-02-12 13:40:16.843 !MESSAGE Failed to execute item copy !STACK 0 org.eclipse.core.commands.NotHandledException: There is no handler to execute for command org.eclipse.ui.edit.copy I assume the Ruleflow editor is not intended to support cut, copy and paste of nodes as was the case in Drools 4, and that this is simply a minor bug to do with the cut, copy and paste menu options not being greyed out, as in drools v4 plugin. Of course, it would be nice to have cut, copy and paste for ruleflow nodes, so perhaps this JIRA could be reclassified as a feature request, if appropriate. -- 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

13 years, 9 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 2009