[JBoss JIRA] Created: (JBIDE-6245) .dsl files from Guvnor examples are not properly read-only.
by Vlado Pakan (JIRA)
.dsl files from Guvnor examples are not properly read-only.
-----------------------------------------------------------
Key: JBIDE-6245
URL: https://jira.jboss.org/jira/browse/JBIDE-6245
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: drools
Environment: Fedora Linux v.11
JBossTools-Update-3.1.0.v201004291720R-H72-GA
Java 1.6Sun JDK
JBoss EAP 5.0
Reporter: Vlado Pakan
Assignee: Kris Verlaenen
.dsl files from Guvnor Repository examples are opened as read-only but it's possible to modified them via .dsl file editor in JBT.
When trying to save this read-only file JBT display this error:
Save Failed
org.guvnor.tools.utils.StringInput cannot be cast to org.eclipse.ui.part.FileEditorInput
It should not be possible to modify read-only .dsl file.
Steps to reproduce:
1. deploy guvnor to server and start server
2. open guvnor perspective
3. add default guvnor repository connection using Guvnor Repositories view
4. right click on newly created Guvnor connection and open Guvnor Console
5. choose ok to empty login dialog and click yes to install Guvnor examples
6. open <Guvnor connection> > pacakges > mortages > ApplicantDsl.dsl file from Guvnor Repositories view
7. select first expresion in opened ApplicantDsl.dsl file and click on edit button
8. click on OK button in Edit Language Mappiing dialog. It's not necessary to make any changes.
9. Choose save for ApplicantDsl.dsl file and error mentioned above is displayed
--
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, 10 months
[JBoss JIRA] Created: (JBIDE-6159) Change Installed Drools Runtimes Preferences Page
by Vlado Pakan (JIRA)
Change Installed Drools Runtimes Preferences Page
-------------------------------------------------
Key: JBIDE-6159
URL: https://jira.jboss.org/jira/browse/JBIDE-6159
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: drools
Affects Versions: 3.1.0.GA
Reporter: Vlado Pakan
Assignee: Kris Verlaenen
Current Installed Drools Runtime Preferences page is little bit confusing (Menu > Window > Preferences > Drools > Installed Drools Runtimes). When user choose button Add... it opens dialog where user can specify Name and Location of existing Drools Runtime or choose button "Create New Drools 5 Runtime" which will open native dialog for selecting directory where to create new Drools Runtime and populate correctly Name and Location text field. This is little bit non standard behavior and user doesn't know what exactly happened.
Better will be to add button "Create..." bellow button "Add..." on the Drools Preferences page with the same functionality as button "Create New Drools 5 Runtime" and remove this button from Drools Runtime dialog. Both actions Create and Add actions will call the same Drools Runtime dialog just with different Title. It would be realy nice to have there some description what is going to happen actually what means Create and what means Add action within Drools Runtime dialog. It also would be nice to have self describing tooltips for buttons "Create..." and "Add..." on Drools Runtime Preferences page.
See attached screenshots.
--
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, 10 months
[JBoss JIRA] Created: (JBIDE-6440) Excel Spreadsheet importing on windows
by Jim Tyrrell (JIRA)
Excel Spreadsheet importing on windows
--------------------------------------
Key: JBIDE-6440
URL: https://jira.jboss.org/browse/JBIDE-6440
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Environment: Windows XP and Excel JBDS 3.0
Reporter: Jim Tyrrell
Attachments: Maximum_Benefits.xls
In my lab yesterday on Windows XP and Excel the importing of the Attached Excel spreadsheet and the created Customer.java resulted in an odd error problems when working with a Drools Project. In the morning session it only affected a few students, in the afternoon it was almost all making me wonder if this is an error that shows up after one or more restarts and recreations of the exact same project. The error was around that the setBenefitAmount is not available, or that there is a not a getter for Age. As you can see they exist, yet this error was there. The error might have gone away with a few saves of the Excel spreadsheet, but not always. Almost appears to me to be related to the load on the machine as in the afternoon a Antivirus scan started, making me think this is an odd timing, building, compiling, etc problem. I have only seen this on windows, and only on a few of the machines in the lab.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months
[JBoss JIRA] Created: (JBIDE-6358) Adding inner class as Fact to guided Rule generates incorrect BRL source
by Vlado Pakan (JIRA)
Adding inner class as Fact to guided Rule generates incorrect BRL source
------------------------------------------------------------------------
Key: JBIDE-6358
URL: https://jira.jboss.org/browse/JBIDE-6358
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: drools
Affects Versions: 3.1.1
Environment: Linux 32bit
JBDS 3.0.1.v201005241821R-H78-GA
JDK Sun 1.6
Reporter: Vlado Pakan
Assignee: Kris Verlaenen
When inner class is used as Fact for guided rule it generates incorrect .brl file with error "BuildError: Unable to resolve ObjectType '<class>$<innerclass>'"
.brl source looks something like this:
<rule>
<name>guided</name>
<modelVersion>1.0</modelVersion>
<attributes/>
<metadataList/>
<lhs>
<fact>
<factType><class>$<innerclass></factType>
</fact>
</lhs>
<rhs/>
</rule>
When .brl file is modified and '$" is replaced with '.' i.e "<factType><class>$<innerclass></factType>" is replaced with "<factType><class>.<innerclass></factType>" error is fixed. .brl file is displayed without errors.
Steps to reproduce:
1. create new Drools Project
2. create new guided rule
3. add "import com.sample.DroolsTest.Message;" line to drools.package file
4. open new guided rule file add new when condition and select "DroolsTest$Message" as Fact type
5. save guided rule file and error will appear in Problems view
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months
[JBoss JIRA] Created: (JBIDE-6248) .brl files from Guvnor examples are not properly read-only.
by Vlado Pakan (JIRA)
.brl files from Guvnor examples are not properly read-only.
-----------------------------------------------------------
Key: JBIDE-6248
URL: https://jira.jboss.org/jira/browse/JBIDE-6248
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: drools
Affects Versions: 3.1.x
Environment: Fedora Linux v.11
JBossTools-Update-3.1.0.v201004291720R-H72-GA
Java 1.6Sun JDK
JBoss EAP 5.0
Reporter: Vlado Pakan
Assignee: Kris Verlaenen
.dsl files from Guvnor Repository examples are opened as read-only but it's possible to modified them via .dsl file editor in JBT.
When trying to save this read-only file JBT display this error:
Save Failed
org.guvnor.tools.utils.StringInput cannot be cast to org.eclipse.ui.part.FileEditorInput
It should not be possible to modify read-only .dsl file.
Steps to reproduce:
1. deploy guvnor to server and start server
2. open guvnor perspective
3. add default guvnor repository connection using Guvnor Repositories view
4. right click on newly created Guvnor connection and open Guvnor Console
5. choose ok to empty login dialog and click yes to install Guvnor examples
6. open <Guvnor connection> > pacakges > mortages > ApplicantDsl.dsl file from Guvnor Repositories view
7. select first expresion in opened ApplicantDsl.dsl file and click on edit button
8. click on OK button in Edit Language Mappiing dialog. It's not necessary to make any changes.
9. Choose save for ApplicantDsl.dsl file and error mentioned above is displayed
--
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, 10 months
[JBoss JIRA] Created: (JBIDE-6247) Bankrupcy history.brl file from Guvnor examples is not opened properly
by Vlado Pakan (JIRA)
Bankrupcy history.brl file from Guvnor examples is not opened properly
----------------------------------------------------------------------
Key: JBIDE-6247
URL: https://jira.jboss.org/jira/browse/JBIDE-6247
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: drools
Affects Versions: 3.1.x
Environment: Fedora Linux v.11
JBossTools-Update-3.1.0.v201004291720R-H72-GA
Java 1.6Sun JDK
JBoss EAP 5.0
Reporter: Vlado Pakan
Assignee: Kris Verlaenen
.scenario files from Guvnor Repository are not opened properly
When trying to open this file JBT display this error:
Could not open the editor: The specified input is not a valid scenario.
Error log:
org.eclipse.emf.ecore.resource.Resource$IOWrappedException: Package with uri 'null' not found. (, 1, 11)
at org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.handleErrors(XMLLoadImpl.java:83)
at org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.load(XMLLoadImpl.java:191)
at org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.doLoad(XMLResourceImpl.java:180)
at org.pi4soa.scenario.ScenarioManager.load(ScenarioManager.java:88)
at org.pi4soa.scenario.designer.editor.ScenarioDesigner.create(ScenarioDesigner.java:408)
at org.pi4soa.scenario.designer.editor.ScenarioDesigner.init(ScenarioDesigner.java:266)
at org.eclipse.ui.internal.EditorManager.createSite(EditorManager.java:798)
at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:644)
at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:462)
at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:595)
at org.eclipse.ui.internal.PartPane.setVisible(PartPane.java:313)
at org.eclipse.ui.internal.presentations.PresentablePart.setVisible(PresentablePart.java:180)
at org.eclipse.ui.internal.presentations.util.PresentablePartFolder.select(PresentablePartFolder.java:270)
at org.eclipse.ui.internal.presentations.util.LeftToRightTabOrder.select(LeftToRightTabOrder.java:65)
at org.eclipse.ui.internal.presentations.util.TabbedStackPresentation.selectPart(TabbedStackPresentation.java:473)
at org.eclipse.ui.internal.PartStack.refreshPresentationSelection(PartStack.java:1256)
at org.eclipse.ui.internal.PartStack.setSelection(PartStack.java:1209)
at org.eclipse.ui.internal.PartStack.showPart(PartStack.java:1608)
at org.eclipse.ui.internal.PartStack.add(PartStack.java:499)
at org.eclipse.ui.internal.EditorStack.add(EditorStack.java:103)
at org.eclipse.ui.internal.PartStack.add(PartStack.java:485)
at org.eclipse.ui.internal.EditorStack.add(EditorStack.java:112)
at org.eclipse.ui.internal.EditorSashContainer.addEditor(EditorSashContainer.java:63)
at org.eclipse.ui.internal.EditorAreaHelper.addToLayout(EditorAreaHelper.java:225)
at org.eclipse.ui.internal.EditorAreaHelper.addEditor(EditorAreaHelper.java:213)
at org.eclipse.ui.internal.EditorManager.createEditorTab(EditorManager.java:778)
at org.eclipse.ui.internal.EditorManager.openEditorFromDescriptor(EditorManager.java:677)
at org.eclipse.ui.internal.EditorManager.openEditor(EditorManager.java:638)
at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2854)
at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2762)
at org.eclipse.ui.internal.WorkbenchPage.access$11(WorkbenchPage.java:2754)
at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:2705)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2701)
at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2685)
at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2668)
at org.guvnor.tools.utils.PlatformUtils.openEditor(PlatformUtils.java:151)
at org.guvnor.tools.views.RepositoryView.doubleClick(RepositoryView.java:448)
at org.guvnor.tools.views.RepositoryView.access$4(RepositoryView.java:435)
at org.guvnor.tools.views.RepositoryView$7.run(RepositoryView.java:405)
at org.guvnor.tools.views.RepositoryView$9.doubleClick(RepositoryView.java:430)
at org.eclipse.jface.viewers.StructuredViewer$1.run(StructuredViewer.java:821)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.runtime.Platform.run(Platform.java:888)
at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:48)
at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)
at org.eclipse.jface.viewers.StructuredViewer.fireDoubleClick(StructuredViewer.java:819)
at org.eclipse.jface.viewers.AbstractTreeViewer.handleDoubleSelect(AbstractTreeViewer.java:1419)
at org.eclipse.jface.viewers.StructuredViewer$4.widgetDefaultSelected(StructuredViewer.java:1195)
at org.eclipse.jface.util.OpenStrategy.fireDefaultSelectionEvent(OpenStrategy.java:238)
at org.eclipse.jface.util.OpenStrategy.access$0(OpenStrategy.java:235)
at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:296)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1176)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3493)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3112)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493)
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:194)
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:368)
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:559)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
at org.eclipse.equinox.launcher.Main.main(Main.java:1287)
Caused by: org.eclipse.emf.ecore.xmi.PackageNotFoundException: Package with uri 'null' not found. (, 1, 11)
at org.eclipse.emf.ecore.xmi.impl.XMLHandler.createObjectByType(XMLHandler.java:1307)
at org.eclipse.emf.ecore.xmi.impl.XMLHandler.createTopObject(XMLHandler.java:1468)
at org.eclipse.emf.ecore.xmi.impl.XMLHandler.processElement(XMLHandler.java:1019)
at org.eclipse.emf.ecore.xmi.impl.XMIHandler.processElement(XMIHandler.java:83)
at org.eclipse.emf.ecore.xmi.impl.XMLHandler.startElement(XMLHandler.java:1001)
at org.eclipse.emf.ecore.xmi.impl.XMLHandler.startElement(XMLHandler.java:712)
at org.eclipse.emf.ecore.xmi.impl.XMIHandler.startElement(XMIHandler.java:169)
at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:501)
at com.sun.org.apache.xerces.internal.impl.dtd.XMLDTDValidator.startElement(XMLDTDValidator.java:767)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:1359)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$ContentDriver.scanRootElementHook(XMLDocumentScannerImpl.java:1317)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:3095)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next(XMLDocumentScannerImpl.java:922)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:648)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:510)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:807)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:107)
at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1205)
at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:522)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:395)
at org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.load(XMLLoadImpl.java:181)
... 75 more
Steps to reproduce:
1. deploy guvnor to server and start server
2. open guvnor perspective
3. add default guvnor repository connection using Guvnor Repositories view
4. right click on newly created Guvnor connection and open Guvnor Console
5. choose ok to empty login dialog and click yes to install Guvnor examples
6. open <Guvnor connection> > pacakges > mortages > Are they old enough.scenario file from Guvnor Repositories view. Error is displayed within editor
--
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, 10 months
[JBoss JIRA] Created: (JBIDE-7798) Drools project wizard : better pre-selection version of generated code
by Libor Zoubek (JIRA)
Drools project wizard : better pre-selection version of generated code
-----------------------------------------------------------------------
Key: JBIDE-7798
URL: https://jira.jboss.org/browse/JBIDE-7798
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: drools
Affects Versions: 3.2.0.Beta2
Reporter: Libor Zoubek
Assignee: Kris Verlaenen
When creating new project, on 3rd page, when user can select drools runtime and select version of drools to generate sample sources.
Selection of 'Generate code compatible with' should filter/depend on drools runtime selection. It makes no sense if you have drools 4.x to allow generating 5.x compatible sources.
Moreover, when user creates new project just entering project name and has as selected 4.x as default runtime. Project with 80 errors is generated.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months