October 2010 - jbosstools-issues - Jboss List Archives

[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, 12 months

5
10
0 / 0

[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, 12 months

4
5
0 / 0

[JBoss JIRA] Created: (JBIDE-7072) Flow Editor - Properties View -> empty when select item for edit (hide editor content)

by Vitali Yemialyanchyk (JIRA)

Flow Editor - Properties View -> empty when select item for edit (hide editor content) -------------------------------------------------------------------------------------- Key: JBIDE-7072 URL: https://jira.jboss.org/browse/JBIDE-7072 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: drools Affects Versions: 3.2.0.M2 Reporter: Vitali Yemialyanchyk Assignee: Kris Verlaenen Priority: Optional -- 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, 12 months

3
5
0 / 0

[JBoss JIRA] Created: (JBDS-1264) DSL Validation

by Jim Tyrrell (JIRA)

DSL Validation -------------- Key: JBDS-1264 URL: https://jira.jboss.org/browse/JBDS-1264 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Environment: All Reporter: Jim Tyrrell When authoring a DLS file you will typically have variable names of the type: "{disabilityType}"=customer: Customer(disabilityType == "{disabilityType}") or something like this. If the Customer object does not exist some sort of problem should be noted in the Problems section. Also a DSL might look like this: {percentage}=eval(customer.disabledPercent >= {percentage}) This to is a little harder as the customer is a variable that is implied. -- 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, 12 months

4
3
0 / 0

[JBoss JIRA] Created: (JBDS-1267) Highlighting a line in the Domain Specific Editor, the Delete key should work

by Jim Tyrrell (JIRA)

Highlighting a line in the Domain Specific Editor, the Delete key should work ----------------------------------------------------------------------------- Key: JBDS-1267 URL: https://jira.jboss.org/browse/JBDS-1267 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Affects Versions: 3.0.1.GA Environment: All Reporter: Jim Tyrrell When I am editing or creating a Domain Specific Language it would be nice to have an Accelerator on the delete key to delete the highlighted line instead of having to click "Remove". It should also be possible to highlight all of them and be able to delete them all, although this might get in the way of what you happens when you click "Edit" -- 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, 12 months

4
4
0 / 0

[JBoss JIRA] Created: (JBIDE-6914) Allow seam-gen style profiles for different environments such as prod and dev

by Samuel Mendenhall (JIRA)

Allow seam-gen style profiles for different environments such as prod and dev ----------------------------------------------------------------------------- Key: JBIDE-6914 URL: https://jira.jboss.org/browse/JBIDE-6914 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Seam Affects Versions: 3.1.1 Reporter: Samuel Mendenhall Assignee: Alexey Kazakov Fix For: 3.2.x A nice feature would be able to build a Seam EAR/WAR based on a defined profile that can be quickly changes such as -Dprofile=prod or -Dprofile-dev, which will allow for say persistence-prod.xml and persistence-dev.xml like in seam-gen. Currently this feature is not in JBDS so deploying to various environments is an added effort when it should be transparent. -- 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, 12 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-6095) Support for CDI implementation libraries selection and/or installation

by Jiri Peterka (JIRA)

Support for CDI implementation libraries selection and/or installation ---------------------------------------------------------------------- Key: JBIDE-6095 URL: https://jira.jboss.org/jira/browse/JBIDE-6095 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: cdi (jsr-299) Affects Versions: 3.1.0.GA Environment: Possibility to automatically select/download CDI implementation libraries into the project when CDI support is enabled. Reporter: Jiri Peterka Fix For: 3.2.next -- 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, 12 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-5811) Code completion for attributes for components without meta-info.

by Alexey Kazakov (JIRA)

Code completion for attributes for components without meta-info. ---------------------------------------------------------------- Key: JBIDE-5811 URL: https://jira.jboss.org/jira/browse/JBIDE-5811 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JSF Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 3.2.next If there is not any metainfo about particular attribute (facelet lib) then we could try to pick up this info from component class using JDT. We should treat all getters/setters as possible attributes. -- 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, 12 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-5769) Switching Seam debug mode.

by Alexey Kazakov (JIRA)

Switching Seam debug mode. -------------------------- Key: JBIDE-5769 URL: https://jira.jboss.org/jira/browse/JBIDE-5769 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Seam Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 3.2.next When user wants to disable Seam debug mode he/she sets debug="false" in components.xml. But it's not enough becouse in this case WEB_INF/dev folder will be ingored in runtime. Our New Seam Web Project sets up /src/hot folder to be deployed to WEB_INF/dev. So this the problem. We should find a way to make this switching more convenient. -- 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, 12 months

1
3
0 / 0

[JBoss JIRA] Created: (JBIDE-5808) Cover CDI model with JUnit test. All relevant cases from TCK should by caverd.

by Alexey Kazakov (JIRA)

Cover CDI model with JUnit test. All relevant cases from TCK should by caverd. ------------------------------------------------------------------------------ Key: JBIDE-5808 URL: https://jira.jboss.org/jira/browse/JBIDE-5808 Project: Tools (JBoss Tools) Issue Type: Task Components: cdi (jsr-299) Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 3.2.next It's quite big work so let's split it into a few parts/subtasks and cover all the cases. -- 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, 12 months

1
8
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues October 2010