December 2010 - jbosstools-issues

[JBoss JIRA] Commented: (JBIDE-7887) Execution Plan for a query executed in Teiid is hard to find in JBDS

by John Doyle (JIRA)

[ https://issues.jboss.org/browse/JBIDE-7887?page=com.atlassian.jira.plugin... ] John Doyle commented on JBIDE-7887: ----------------------------------- Agree that we should eliminate the menu and just always display the plan. We are however limited in what we can display in that view. Don't know if I can get an XML viewer in there. Will have to see. > Execution Plan for a query executed in Teiid is hard to find in JBDS > -------------------------------------------------------------------- > > Key: JBIDE-7887 > URL: https://issues.jboss.org/browse/JBIDE-7887 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: teiid > Reporter: Ramesh Reddy > Assignee: John Doyle > Fix For: 3.2.0.CR1 > > > Currently viewing of the execution plan is little cumbersome, it is not readily available as it did previous incarnation of the MetaMatrix Designer. Currently, the user needs to right click on the query and select "Teiid_7.1 --> Query Plan" see the query plan. > When a query is executed, the statement executed has the query already associated with it, so there is no good reason for user to take yet another step before they can see the query plan. It should be automatically populated in the "Execution Plan" tab when the query is executed. Or provide tool bar button on the "SQL Results" panel, that will take user to the "Execution Plan" of the current query. In case of query plan not available this tool bar button could be greyed out. > Since the query plan is in XML, show it in XML editor (read-only), that will let the user collapse or expand the the nodes to see and understand it, otherwise these are rather long, could be confusing to scroll. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBIDE-7846) Unable to load dialect Error in Drools project

by Vlado Pakan (JIRA)

Unable to load dialect Error in Drools project ---------------------------------------------- Key: JBIDE-7846 URL: https://jira.jboss.org/browse/JBIDE-7846 Project: Tools (JBoss Tools) Issue Type: Bug Components: drools Affects Versions: 3.2.0.Beta2 Environment: JBDS 4.0.0.v201012070137R-H33-Beta2 linux 32bit Reporter: Vlado Pakan Assignee: Kris Verlaenen Attachments: droolserror.png When new Drools project is created there is this error: Unable to load dialect 'org.drools.rule.builder.dialect.mvel.MVELDialectConfiguration:mvel:org.drools.rule.builder.dialect.mvel.MVELDialectConfiguration' See attached screenshot. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-7881) In Seam perspective -> Properties View -> Fast View in context menu does not work

by Vitali Yemialyanchyk (JIRA)

In Seam perspective -> Properties View -> Fast View in context menu does not work --------------------------------------------------------------------------------- Key: JBIDE-7881 URL: https://issues.jboss.org/browse/JBIDE-7881 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.2.0.Beta2 Reporter: Vitali Yemialyanchyk Assignee: Alexey Kazakov Priority: Critical Fast View in context menu is always checked - not possible to uncheck it -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

3
6
0 / 0

[JBoss JIRA] Created: (JBIDE-7879) In Seam perspective dragging Properties View hangle whole Eclipse only Eclipse restart will help

by Vitali Yemialyanchyk (JIRA)

In Seam perspective dragging Properties View hangle whole Eclipse only Eclipse restart will help ------------------------------------------------------------------------------------------------ Key: JBIDE-7879 URL: https://issues.jboss.org/browse/JBIDE-7879 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.2.0.Beta2 Reporter: Vitali Yemialyanchyk Assignee: Alexey Kazakov Priority: Blocker Attachments: screenshot-1.jpg close Properties View in Seam perspective, open it, try to drag it and drop in some other place - I get Eclipse no response on any input. look at screenshots, only Eclipse restart could help, reproducible only in Seam perspective. This exception is in Error Log: Unhandled event loop exception java.lang.ArrayIndexOutOfBoundsException: -1 at java.util.ArrayList.get(Unknown Source) at org.eclipse.ui.internal.presentations.PresentationSerializer.getPart(PresentationSerializer.java:48) at org.eclipse.ui.internal.presentations.util.LeftToRightTabOrder.restoreState(LeftToRightTabOrder.java:97) at org.eclipse.ui.internal.presentations.util.TabbedStackPresentation.restoreState(TabbedStackPresentation.java:206) at org.eclipse.ui.internal.presentations.PresentationFactoryUtil.createPresentation(PresentationFactoryUtil.java:58) at org.eclipse.ui.internal.PartStack.createControl(PartStack.java:571) at org.eclipse.ui.internal.PartSashContainer.replace(PartSashContainer.java:794) at org.eclipse.ui.internal.ViewSashContainer.replace(ViewSashContainer.java:316) at org.eclipse.ui.internal.PerspectiveHelper.addPart(PerspectiveHelper.java:377) at org.eclipse.ui.internal.Perspective.removeFastView(Perspective.java:1192) at org.eclipse.ui.internal.Perspective.removeFastView(Perspective.java:1167) at org.eclipse.ui.internal.WorkbenchPage.removeFastView(WorkbenchPage.java:2988) at org.eclipse.ui.internal.FastViewManager.makeFast(FastViewManager.java:380) at org.eclipse.ui.internal.FastViewManager.removeViewReference(FastViewManager.java:360) at org.eclipse.ui.internal.PerspectiveHelper.derefPart(PerspectiveHelper.java:714) at org.eclipse.ui.internal.ViewSashContainer.derefPart(ViewSashContainer.java:278) at org.eclipse.ui.internal.PartSashContainer.stack(PartSashContainer.java:1244) at org.eclipse.ui.internal.PartSashContainer.dropObject(PartSashContainer.java:1210) at org.eclipse.ui.internal.PartSashContainer$SashContainerDropTarget.drop(PartSashContainer.java:132) at org.eclipse.ui.internal.dnd.DragUtil.performDrag(DragUtil.java:134) at org.eclipse.ui.internal.FastViewPane$2.dragStart(FastViewPane.java:161) at org.eclipse.ui.internal.FastViewPane$2.dragStart(FastViewPane.java:136) at org.eclipse.ui.internal.presentations.util.TabbedStackPresentation$1.handleEvent(TabbedStackPresentation.java:118) at org.eclipse.ui.internal.presentations.util.AbstractTabFolder.fireEvent(AbstractTabFolder.java:269) at org.eclipse.ui.internal.presentations.util.AbstractTabFolder.fireEvent(AbstractTabFolder.java:282) at org.eclipse.ui.internal.presentations.util.AbstractTabFolder.handleDragStarted(AbstractTabFolder.java:366) at org.eclipse.ui.internal.presentations.util.AbstractTabFolder$2.handleEvent(AbstractTabFolder.java:67) at org.eclipse.ui.presentations.PresentationUtil.handleMouseMove(PresentationUtil.java:110) at org.eclipse.ui.presentations.PresentationUtil.access$4(PresentationUtil.java:95) at org.eclipse.ui.presentations.PresentationUtil$2.handleEvent(PresentationUtil.java:63) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4066) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3657) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) 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:369) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574) at org.eclipse.equinox.launcher.Main.run(Main.java:1407) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

3
15
0 / 0

[JBoss JIRA] Created: (JBIDE-7811) Wizard to create a new Infinispan unit test

by Manik Surtani (JIRA)

Wizard to create a new Infinispan unit test ------------------------------------------- Key: JBIDE-7811 URL: https://jira.jboss.org/browse/JBIDE-7811 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: infinispan Reporter: Manik Surtani Assignee: Max Andersen Same reasoning as declared in ISPN-818, except that this is within the IDE to further encourage users to submit tests. Again, this could depend on ISPN-818 for the Maven Archetype. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

2
3
0 / 0

[JBoss JIRA] Commented: (JBIDE-717) When format the components.xml using the xml formatter of eclipse and then save the file, the xml is becoming a mess (it totally breaks the format)

by Max Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-717?page=com.atlassian.jira.plugin.... ] Max Andersen commented on JBIDE-717: ------------------------------------ Cleaning the gutters. Closing old bug reports with no updates the last 18 months. If you feel this close was unwarranted then please reopen or create a new one with link to the old and we will revisit. > When format the components.xml using the xml formatter of eclipse and then save the file, the xml is becoming a mess (it totally breaks the format) > --------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-717 > URL: https://issues.jboss.org/browse/JBIDE-717 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: XML Structured Editor > Environment: windows xp, RHDS beta 1, jdk 1.5_0.12 > Reporter: Adrian Mitev > Fix For: LATER > > Attachments: after save.jpg, before save.jpg > > > This was also happening when editing faces-config file with exadel studio. Here are two images: the code before saving and the code after saving. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBIDE-717) When format the components.xml using the xml formatter of eclipse and then save the file, the xml is becoming a mess (it totally breaks the format)

by Max Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-717?page=com.atlassian.jira.plugin.... ] Max Andersen resolved JBIDE-717. -------------------------------- Resolution: Out of Date > When format the components.xml using the xml formatter of eclipse and then save the file, the xml is becoming a mess (it totally breaks the format) > --------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-717 > URL: https://issues.jboss.org/browse/JBIDE-717 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: XML Structured Editor > Environment: windows xp, RHDS beta 1, jdk 1.5_0.12 > Reporter: Adrian Mitev > Fix For: LATER > > Attachments: after save.jpg, before save.jpg > > > This was also happening when editing faces-config file with exadel studio. Here are two images: the code before saving and the code after saving. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBIDE-621) Traditional Chinese Input Failed in Visual Page Editor

by Max Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-621?page=com.atlassian.jira.plugin.... ] Max Andersen closed JBIDE-621. ------------------------------ Resolution: Out of Date > Traditional Chinese Input Failed in Visual Page Editor > ------------------------------------------------------ > > Key: JBIDE-621 > URL: https://issues.jboss.org/browse/JBIDE-621 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Visual Page Editor Templates > Affects Versions: ExadelStudioPro4 > Environment: Eclipse 3.2.2+Exadel Studio Pro 4.0.4+Tomcat 5.5+Windows XP Home(US English) > Reporter: KT Lo > Assignee: Maxim Areshkau > Fix For: LATER > > Attachments: Chinese.png, editing.zip, screenshot-1.jpg, screenshot-1.jpg, screenshot-2.jpg, screenshot-3.jpg > > > Step 1: Called Up Traditional Chinese Phonetic Input Method (Check ScreenShot:"Step1) > Step2: Intended Chinese Character typed but not showed and in the VIsual Page Editor ( (Check ScreenShot:"Step2) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBIDE-621) Traditional Chinese Input Failed in Visual Page Editor

by Max Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-621?page=com.atlassian.jira.plugin.... ] Max Andersen commented on JBIDE-621: ------------------------------------ Cleaning the gutters. Closing old bug reports with no updates the last 18 months. If you feel this close was unwarranted then please reopen or create a new one with link to the old and we will revisit. > Traditional Chinese Input Failed in Visual Page Editor > ------------------------------------------------------ > > Key: JBIDE-621 > URL: https://issues.jboss.org/browse/JBIDE-621 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Visual Page Editor Templates > Affects Versions: ExadelStudioPro4 > Environment: Eclipse 3.2.2+Exadel Studio Pro 4.0.4+Tomcat 5.5+Windows XP Home(US English) > Reporter: KT Lo > Assignee: Maxim Areshkau > Fix For: LATER > > Attachments: Chinese.png, editing.zip, screenshot-1.jpg, screenshot-1.jpg, screenshot-2.jpg, screenshot-3.jpg > > > Step 1: Called Up Traditional Chinese Phonetic Input Method (Check ScreenShot:"Step1) > Step2: Intended Chinese Character typed but not showed and in the VIsual Page Editor ( (Check ScreenShot:"Step2) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (RHDS-172) There is no opportunity to select existent Group for shortcuts under Linux

by Anton Klimkovich (JIRA)

There is no opportunity to select existent Group for shortcuts under Linux -------------------------------------------------------------------------- Key: RHDS-172 URL: http://jira.jboss.com/jira/browse/RHDS-172 Project: Red Hat Developer Studio Issue Type: Bug Components: installer Affects Versions: 1.0.0.beta1 Reporter: Anton Klimkovich Priority: Minor Step 9 in installer Can't select any other existent group. Look at screenshot -- 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, 4 months

3
6
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 December 2010