December 2010 - jbosstools-issues

[JBoss JIRA] Created: (TOOLSDOC-132) update jboss tools doc nightly build

by Max Andersen (JIRA)

update jboss tools doc nightly build ------------------------------------ Key: TOOLSDOC-132 URL: https://issues.jboss.org/browse/TOOLSDOC-132 Project: Documentation for JBoss Tools/Developer Studio Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Max Andersen Assignee: Isaac Rooskov Fix For: 3.0.0.GA >From Isaac: Cloud documentation (contains Deltacloud documentation): <directory>../../deltacloud/docs/Cloud_Tools_Reference_Guide/target/docbook/publish/en-US</directory> <outputDirectory>/cloud</outputDirectory> and ModeShape doc: <directory>../../modeshape/docs/ModeShape_Tools_Reference_Guide/target/docbook/publish/en-US</directory> <outputDirectory>/modeshape</outputDirectory> Nightly build needs updating -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

2
7
0 / 0

[JBoss JIRA] Created: (JBDS-1460) No obvious icon is present to launch JBDS after installation on Mac

by Denis Golovin (JIRA)

No obvious icon is present to launch JBDS after installation on Mac ------------------------------------------------------------------- Key: JBDS-1460 URL: https://issues.jboss.org/browse/JBDS-1460 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Components: installer Affects Versions: 4.0.0.Beta1 Environment: Mac OS X 10.6 (Snow Leopard) w/ Cocoa Reporter: John Verhaeg Assignee: Denis Golovin Fix For: 4.0.0.CR1 After installation, I get the jbdevstudio folder, but nothing in it but other folders and a readme that talks about "clicking on the installed icon in your program menu or desktop" that doesn't exist. Just browsing for something to launch, my first inclination was to look in the studio subfolder, and only after discovering there's nothing appropriate there, and knowing, as a developer for Teiid Designer, that dev studio is an Eclipse application, did I deduce that I must have to launch the eclipse application under the eclipse subfolder. This definitely isn't intuitive, and especially wouldn't be for those new to dev studio and/or Eclipse. I'd want to see an app icon directly in my Applications folder, not even within the jbdevstudio folder. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

1
2
0 / 0

[JBoss JIRA] Updated: (JBDS-1460) No obvious icon is present to launch JBDS after installation on Mac

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-1460?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-1460: -------------------------------- Component/s: P2 Enabled Product Installer (was: installer) > No obvious icon is present to launch JBDS after installation on Mac > ------------------------------------------------------------------- > > Key: JBDS-1460 > URL: https://issues.jboss.org/browse/JBDS-1460 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: P2 Enabled Product Installer > Affects Versions: 4.0.0.Beta1 > Environment: Mac OS X 10.6 (Snow Leopard) w/ Cocoa > Reporter: John Verhaeg > Assignee: Denis Golovin > Fix For: 4.0.0.CR1 > > > After installation, I get the jbdevstudio folder, but nothing in it but other folders and a readme that talks about "clicking on the installed icon in your program menu or desktop" that doesn't exist. Just browsing for something to launch, my first inclination was to look in the studio subfolder, and only after discovering there's nothing appropriate there, and knowing, as a developer for Teiid Designer, that dev studio is an Eclipse application, did I deduce that I must have to launch the eclipse application under the eclipse subfolder. This definitely isn't intuitive, and especially wouldn't be for those new to dev studio and/or Eclipse. I'd want to see an app icon directly in my Applications folder, not even within the jbdevstudio folder. -- 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] Updated: (JBIDE-7884) Unable to get the default Bean Validation; missing javax.validation.Validation

by Jacek Grzebyta (JIRA)

[ https://issues.jboss.org/browse/JBIDE-7884?page=com.atlassian.jira.plugin... ] Jacek Grzebyta updated JBIDE-7884: ---------------------------------- Attachment: stackTrace.log newEmptyPhibase-2010-12-08.sql schema > Unable to get the default Bean Validation; missing javax.validation.Validation > ------------------------------------------------------------------------------ > > Key: JBIDE-7884 > URL: https://issues.jboss.org/browse/JBIDE-7884 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Bean Validation > Affects Versions: 3.3.x > Environment: OS: Windows, Eclipse: eclipse.buildId=M20100909-0800, java: -product org.eclipse.epp.package.jee.product -vm C:/Java/jdk1.6.0_21/bin/javaw.exe, Hibernate Tools: 3.3.0.v20101213-0459-H358-CR1org.hibernate.eclipse.feature.feature.group > Reporter: Jacek Grzebyta > Assignee: Max Andersen > Labels: Ivy, javax.validation.Validation, validation > Attachments: newEmptyPhibase-2010-12-08.sql, stackTrace.log > > > I am developing project Phibase. The source is here: http://phibase2.svn.sourceforge.net/viewvc/phibase2/trunk/org.phibase.dat... and database config file here: http://phibase2.svn.sourceforge.net/viewvc/phibase2/trunk/org.phibase.dat... I cannot rebuild configuration and I have error: org.hibernate.HibernateException: Unable to get the default Bean Validation factory. Stack track shows it's missing javax.validation.Validation. However this class occurs in ivy dependencies (look at ivy.xml). This error doesn't occurs in linux environment. -- 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] Updated: (JBIDE-7879) In Seam perspective dragging Properties View hangle whole Eclipse only Eclipse restart will help

by Vitali Yemialyanchyk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-7879?page=com.atlassian.jira.plugin... ] Vitali Yemialyanchyk updated JBIDE-7879: ---------------------------------------- Attachment: screenshot-1.jpg > 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

1
0
0 / 0

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

by John Doyle (JIRA)

[ https://issues.jboss.org/browse/JBDS-1458?page=com.atlassian.jira.plugin.... ] John Doyle reassigned JBDS-1458: -------------------------------- Assignee: John Doyle > Execution Plan for a query executed in Teiid is hard to find in JBDS > -------------------------------------------------------------------- > > Key: JBDS-1458 > URL: https://issues.jboss.org/browse/JBDS-1458 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: teiid > Reporter: Ramesh Reddy > Assignee: John Doyle > > 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] Moved: (JBDS-1458) Execution Plan for a query executed in Teiid is hard to find in JBDS

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/JBDS-1458?page=com.atlassian.jira.plugin.... ] Van Halbert moved SOA-2672 to JBDS-1458: ---------------------------------------- Project: Developer Studio (JBoss Developer Studio) (was: JBoss Enterprise SOA Platform) Key: JBDS-1458 (was: SOA-2672) Security: (was: Public) Component/s: teiid (was: EDS) > Execution Plan for a query executed in Teiid is hard to find in JBDS > -------------------------------------------------------------------- > > Key: JBDS-1458 > URL: https://issues.jboss.org/browse/JBDS-1458 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: teiid > Reporter: Ramesh Reddy > > 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: (TOOLSDOC-100) JBDS40_002 WSDL from POJO

by Isaac Rooskov (JIRA)

JBDS40_002 WSDL from POJO ------------------------- Key: TOOLSDOC-100 URL: https://jira.jboss.org/browse/TOOLSDOC-100 Project: Documentation for JBoss Tools/Developer Studio Issue Type: Task Security Level: Public (Everyone can see) Reporter: Isaac Rooskov Assignee: Isaac Rooskov Priority: Blocker Tracker for this issue. Status: Committed Info coming from Brian Fitzpatrick -- 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

15 years, 4 months

2
9
0 / 0

[JBoss JIRA] Created: (TOOLSDOC-105) JBDS40_013 ModeShape plug-in for Teiid

by Isaac Rooskov (JIRA)

JBDS40_013 ModeShape plug-in for Teiid -------------------------------------- Key: TOOLSDOC-105 URL: https://jira.jboss.org/browse/TOOLSDOC-105 Project: Documentation for JBoss Tools/Developer Studio Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Reporter: Isaac Rooskov Assignee: Isaac Rooskov Priority: Blocker Tracker for this issue. Status: Committed but scope of documentation required is unknown -- 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

15 years, 4 months

2
9
0 / 0

[JBoss JIRA] Deleted: (JBDS-1437) Bundle org.jboss.tools.equinox.transforms.xslt@1:start not found.

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-1437?page=com.atlassian.jira.plugin.... ] Denis Golovin deleted JBDS-1437: -------------------------------- > Bundle org.jboss.tools.equinox.transforms.xslt@1:start not found. > ----------------------------------------------------------------- > > Key: JBDS-1437 > URL: https://issues.jboss.org/browse/JBDS-1437 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Reporter: Dmitry Geraskov > Assignee: Denis Golovin > Priority: Critical > > To reproduce: > download and install jbdevstudio-eap-win32-4.0.0.v201011220647N-H191-Beta2.jar (I use Windows XP) > Run jbds on empty workspace. > There are 2 errors in Error log without stacktraces: > Bundle org.jboss.tools.equinox.transforms.xslt@1:start not found. > and https://jira.jboss.org/browse/TEIIDDES-725 -- 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

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