January 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-1961) DSLR: Expander in comment-line seams to be treaten as active

by Norbert Ziegler (JIRA)

DSLR: Expander in comment-line seams to be treaten as active ------------------------------------------------------------ Key: JBRULES-1961 URL: https://jira.jboss.org/jira/browse/JBRULES-1961 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler Affects Versions: 5.0.0.M5 Environment: Eclipse3.4, WinXP, jre6u10 Reporter: Norbert Ziegler Assignee: Mark Proctor Priority: Minor Having an DSLR-File where I sometimes want to switch from expander-1 to expander-2 (only one of them is active). Therefor the DSLR looks like follows: expander myexpander1.dsl # expander myexpander2. dsl This works, but only because I entered an additional blank before the commented second dsl-suffix If you write # expander myexpander2.dsl as it should be normal the commented line seems to be treaten as "active" an that leeds to several errors. E.g.: switching to the DRL Viewer you get an "Internal error in Drools Plugin:" java.lang.IllegalArgumentException: Could not find dsl definition. at org.drools.eclipse.dsl.editor.DSLRuleEditor2.setFocus(Unknown Source) at org.eclipse.ui.part.MultiPageEditorPart.pageChange(MultiPageEditorPart.java:738) at org.eclipse.ui.forms.editor.FormEditor.pageChange(FormEditor.java:509) at org.eclipse.ui.part.MultiPageEditorPart$2.widgetSelected(MultiPageEditorPart.java:266) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:228) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1027) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1012) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:770) at org.eclipse.swt.custom.CTabFolder.setSelection(CTabFolder.java:3242) at org.eclipse.swt.custom.CTabFolder.onMouse(CTabFolder.java:2017) at org.eclipse.swt.custom.CTabFolder$1.handleEvent(CTabFolder.java:320) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3823) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3422) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2382) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2198) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:488) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:193) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:386) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504) at org.eclipse.equinox.launcher.Main.run(Main.java:1236) at org.eclipse.equinox.launcher.Main.main(Main.java:1212) and you get a popup with title "DSL Rule Translation Error". -- 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

15 years, 2 months

3
3
0 / 0

[JBoss JIRA] Created: (JBRULES-766) The Eclipse IDE plugin should be split in a runtime and ui plugins

by Christophe Avare (JIRA)

The Eclipse IDE plugin should be split in a runtime and ui plugins ------------------------------------------------------------------ Key: JBRULES-766 URL: http://jira.jboss.com/jira/browse/JBRULES-766 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Eclipse IDE Affects Versions: 3.0.5 Environment: Eclipse 3.2 + JBRULES 3.0.5 Reporter: Christophe Avare Assigned To: Mark Proctor Priority: Minor This is a return of experience after working with Eclipse + JBRules on a medium-sized project. It happens that the deployement of the org.drools.ide plugin on a end user workstation clutters the ui with unwanted features and we had to refactor it so that the libs are packaged on a plugin of their own, the UI stuff in another, not deployed, plugin. -- 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

15 years, 2 months

3
3
0 / 0

[JBoss JIRA] Created: (JBRULES-581) Pair Matching in DRL editor

by Kris Verlaenen (JIRA)

Pair Matching in DRL editor --------------------------- Key: JBRULES-581 URL: http://jira.jboss.com/jira/browse/JBRULES-581 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Eclipse IDE Reporter: Kris Verlaenen Assigned To: Kris Verlaenen DRL editor should show matching bracket for '(', ')', '[', ']', '{' and '}' It should support auto-adding of closing bracket when typing opening bracket 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

15 years, 2 months

3
2
0 / 0

[JBoss JIRA] Created: (JBRULES-568) IDE to understand new XXX.package rule package config file, and support 1 rule per file "convention" to sync with repository

by Michael Neale (JIRA)

IDE to understand new XXX.package rule package config file, and support 1 rule per file "convention" to sync with repository ---------------------------------------------------------------------------------------------------------------------------- Key: JBRULES-568 URL: http://jira.jboss.com/jira/browse/JBRULES-568 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 3.1-m3 Reporter: Michael Neale Assigned To: Kris Verlaenen Fix For: 3.1-m3 package layout will be something like: /<RulePackageName>.package - has imports in it etc... /Rule Name 1.rule (vanilla DRL) /Rule Name 2.brule (uses DSL) /XXX.dsl (used by brule file) None of the atomic rule files will have package name, or anything other then when/then/attributes, the IDE will have to look in to the .package file to find this out. .drl files can work as they do now. Let me know if this is a dupe ;) -- 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

15 years, 2 months

4
7
0 / 0

[JBoss JIRA] Created: (JBRULES-493) Remember selected working memory for debug views

by Mark Proctor (JIRA)

Remember selected working memory for debug views ------------------------------------------------ Key: JBRULES-493 URL: http://jira.jboss.com/jira/browse/JBRULES-493 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Eclipse IDE Reporter: Mark Proctor Assigned To: Kris Verlaenen Fix For: 3.1-m1 When you select working memory it should remember that instance, so when you are propagating through the network you shouldn't have to keep re-selecting it to view data. Better yet we should have another debug view that collects working memory instances as it "realises" them during debug runtime, the current one is highlighed and a different current can easily be selected. -- 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

15 years, 2 months

3
5
0 / 0

[JBoss JIRA] Created: (JBRULES-775) tree views should remember open/close toggle

by Mark Proctor (JIRA)

tree views should remember open/close toggle -------------------------------------------- Key: JBRULES-775 URL: http://jira.jboss.com/jira/browse/JBRULES-775 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Eclipse IDE Reporter: Mark Proctor Assigned To: Kris Verlaenen Fix For: 3.1-m2 When using the views, such as agenda view, they keep expanding everything, when you have a large number of entries having to repeatedly re-adjust the layout of the tree view is annoying. -- 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

15 years, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (JBRULES-776) Working Memory View by Object Type

by Mark Proctor (JIRA)

Working Memory View by Object Type ---------------------------------- Key: JBRULES-776 URL: http://jira.jboss.com/jira/browse/JBRULES-776 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Mark Proctor Assigned To: Kris Verlaenen Fix For: 3.1-m2 It would be nice in the Working Memory view if we could also view by object type. -- 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

15 years, 2 months

2
5
0 / 0

[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

15 years, 2 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

15 years, 2 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

15 years, 2 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 January 2011