December 2009 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-5274) Copy/Move JBT project configuration dialogs to Project->Configure menu.

by Alexey Kazakov (JIRA)

Copy/Move JBT project configuration dialogs to Project->Configure menu. ----------------------------------------------------------------------- Key: JBIDE-5274 URL: https://jira.jboss.org/jira/browse/JBIDE-5274 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 3.1.0.CR1 -- 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, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (JBDS-1003) the latest builds of JBDS RC1 are broken. EAP 5 isn't included in build.

by Anton Klimkovich (JIRA)

the latest builds of JBDS RC1 are broken. EAP 5 isn't included in build. ------------------------------------------------------------------------- Key: JBDS-1003 URL: https://jira.jboss.org/jira/browse/JBDS-1003 Project: JBoss Developer Studio Issue Type: Bug Components: Build Affects Versions: 3.0.0.CR1 Environment: jbdevstudio-eap-win32-3.0.0.v200912042231M-H29-RC1 Reporter: Anton Klimkovich Priority: Critical Builds from http://reports.qa.atl.jboss.com/binaries/RHDS/builds/release/3.0.0.RC1 are broken. EAP 5 isn't included in build jbdevstudio-eap-win32-3.0.0.v200912042231M-H29-RC1 Start splashscreen with logo is missed. Seam perspective isn't loaded by default. -- 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, 6 months

2
4
0 / 0

[JBoss JIRA] Created: (JBIDE-5574) XPCOM exception under Linux 64 after closing a file

by Yura Zhishko (JIRA)

XPCOM exception under Linux 64 after closing a file --------------------------------------------------- Key: JBIDE-5574 URL: https://jira.jboss.org/jira/browse/JBIDE-5574 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 3.1.0.CR1 Reporter: Yura Zhishko Assignee: Yura Zhishko Fix For: 3.1.0.CR2 After closing a file in Linux 64 I've got the next exception: org.mozilla.xpcom.XPCOMException: The function "removeProgressListener" returned an error condition (0x80004005) at org.mozilla.xpcom.internal.XPCOMJavaProxy.callXPCOMMethod(Native Method) at org.mozilla.xpcom.internal.XPCOMJavaProxy.invoke(XPCOMJavaProxy.java:143) at $Proxy6.removeProgressListener(Unknown Source) at org.jboss.tools.vpe.xulrunner.editor.XulRunnerEditor$2.widgetDisposed(XulRunnerEditor.java:171) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:117) 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.Widget.sendEvent(Widget.java:1200) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1185) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1025) at org.eclipse.swt.browser.Mozilla$6.handleEvent(Mozilla.java:1484) 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.Widget.sendEvent(Widget.java:1200) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1181) at org.eclipse.swt.widgets.Widget.release(Widget.java:1044) at org.eclipse.swt.widgets.Control.release(Control.java:3293) at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:1185) at org.eclipse.swt.widgets.Widget.release(Widget.java:1047) at org.eclipse.swt.widgets.Control.release(Control.java:3293) at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:1185) at org.eclipse.swt.widgets.Widget.release(Widget.java:1047) at org.eclipse.swt.widgets.Control.release(Control.java:3293) at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:1185) at org.eclipse.swt.widgets.Widget.release(Widget.java:1047) at org.eclipse.swt.widgets.Control.release(Control.java:3293) at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:1185) at org.eclipse.swt.widgets.Widget.release(Widget.java:1047) at org.eclipse.swt.widgets.Control.release(Control.java:3293) at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:1185) at org.eclipse.swt.widgets.Widget.release(Widget.java:1047) at org.eclipse.swt.widgets.Control.release(Control.java:3293) at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:1185) at org.eclipse.swt.widgets.Widget.release(Widget.java:1047) at org.eclipse.swt.widgets.Control.release(Control.java:3293) at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:1185) at org.eclipse.swt.widgets.Widget.release(Widget.java:1047) at org.eclipse.swt.widgets.Control.release(Control.java:3293) at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:1185) at org.eclipse.swt.widgets.Widget.release(Widget.java:1047) at org.eclipse.swt.widgets.Control.release(Control.java:3293) at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:1185) at org.eclipse.swt.widgets.Widget.release(Widget.java:1047) at org.eclipse.swt.widgets.Control.release(Control.java:3293) at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:1185) at org.eclipse.swt.widgets.Widget.release(Widget.java:1047) at org.eclipse.swt.widgets.Control.release(Control.java:3293) at org.eclipse.swt.widgets.Widget.dispose(Widget.java:446) at org.eclipse.ui.internal.PartPane.dispose(PartPane.java:180) at org.eclipse.ui.internal.WorkbenchPartReference.dispose(WorkbenchPartReference.java:681) at org.eclipse.ui.internal.WorkbenchPage.disposePart(WorkbenchPage.java:1715) at org.eclipse.ui.internal.WorkbenchPage.handleDeferredEvents(WorkbenchPage.java:1422) at org.eclipse.ui.internal.WorkbenchPage.deferUpdates(WorkbenchPage.java:1406) at org.eclipse.ui.internal.WorkbenchPage.closeEditors(WorkbenchPage.java:1380) at org.eclipse.ui.internal.WorkbenchPage.closeEditor(WorkbenchPage.java:1435) at org.eclipse.ui.internal.EditorPane.doHide(EditorPane.java:61) at org.eclipse.ui.internal.PartStack.close(PartStack.java:543) at org.eclipse.ui.internal.EditorStack.close(EditorStack.java:206) at org.eclipse.ui.internal.PartStack$1.close(PartStack.java:122) at org.eclipse.ui.internal.presentations.util.TabbedStackPresentation$1.handleEvent(TabbedStackPresentation.java:83) at org.eclipse.ui.internal.presentations.util.AbstractTabFolder.fireEvent(AbstractTabFolder.java:270) at org.eclipse.ui.internal.presentations.util.AbstractTabFolder.fireEvent(AbstractTabFolder.java:279) at org.eclipse.ui.internal.presentations.defaultpresentation.DefaultTabFolder.access$1(DefaultTabFolder.java:1) at org.eclipse.ui.internal.presentations.defaultpresentation.DefaultTabFolder$1.closeButtonPressed(DefaultTabFolder.java:70) at org.eclipse.ui.internal.presentations.PaneFolder.notifyCloseListeners(PaneFolder.java:626) at org.eclipse.ui.internal.presentations.PaneFolder$3.close(PaneFolder.java:206) at org.eclipse.swt.custom.CTabFolder.onMouse(CTabFolder.java:2199) at org.eclipse.swt.custom.CTabFolder$1.handleEvent(CTabFolder.java:327) 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:585) 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) -- 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, 6 months

1
2
0 / 0

[JBoss JIRA] Created: (JBIDE-5569) Issues around Autocreation of hibernate console config on seam+jpa projects

by Max Rydahl Andersen (JIRA)

Issues around Autocreation of hibernate console config on seam+jpa projects --------------------------------------------------------------------------- Key: JBIDE-5569 URL: https://jira.jboss.org/jira/browse/JBIDE-5569 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.1.0.CR1 Reporter: Max Rydahl Andersen Assignee: Dmitry Geraskov Fix For: 3.1.0.CR2 >From JBIDE-4985: The location of the .launch is only different when JPA facet is selected and hibernate platform enabled. We need to look at that for CR2. For CR1 not important. Issue is to get uniform projects so locations of file should be stable as possible. In CR2 possibly introduce an option about hat behavior we want. -- 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, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-5496) new runtime wizard very annoying, version not updated

by Rob Stryker (JIRA)

new runtime wizard very annoying, version not updated ----------------------------------------------------- Key: JBIDE-5496 URL: https://jira.jboss.org/jira/browse/JBIDE-5496 Project: Tools (JBoss Tools) Issue Type: Bug Components: esb Affects Versions: 3.1.0.M4 Reporter: Rob Stryker Assignee: Denny Xu Fix For: 3.1.0.CR1 When creating a new runtime, if I point to soa-p-4.3.0 directory, and select 4.7 as the version, it rpesents an error and tells me the version is wrong. But it does not select the correct one. So then I try to set version to 4.6, and it still says error, so I try 4.5, and still error, and so I try 4.4 and it works. This is very annoying for the user -- 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, 6 months

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-5410) Can not deploy ESB 4.7 project to server using Run As -> Run on Server

by Denny Xu (JIRA)

Can not deploy ESB 4.7 project to server using Run As -> Run on Server ---------------------------------------------------------------------- Key: JBIDE-5410 URL: https://jira.jboss.org/jira/browse/JBIDE-5410 Project: Tools (JBoss Tools) Issue Type: Bug Components: esb Affects Versions: 3.1.0.M4 Reporter: Denny Xu Assignee: Denny Xu Fix For: 3.1.0.CR1 I created a new ESB Project using latest nightly build of JBoss Tools and selected 4.7 as the JBoss ESB version and Target Runtime of JBoss 5.1 Runtime. When I try to deploy the project on the server (Run As -> Run on Server) I get the message " The selection is not within a valid module". -- 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, 6 months

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-5453) When initializer is created, it appears to be selected but its text is not displayed

by Brad Maxwell (JIRA)

When initializer is created, it appears to be selected but its text is not displayed ------------------------------------------------------------------------------------ Key: JBIDE-5453 URL: https://jira.jboss.org/jira/browse/JBIDE-5453 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpm Affects Versions: 3.1.0.M4 Environment: Eclipse 3.5 jee-galileo-SR1 + JBossTools 3.1 v1.0.0.v200912010817N-H2-RC1 Reporter: Brad Maxwell Priority: Minor 1) Add an Assign 2) Click Details for the Assign 3) Click new to create a new mapping 4) Map input.payload/input to output.payload/result 5) Click away 6) It will ask you if you want to create an initializer 7) Click Yes 8) It will create a mapping above the "Variable to Variable" called "Fixed Value to Variable" 9) The "Fixed Value to Variable" appears to be selected / highlighted, however what is displayed in the text box is the text for the "Variable to Variable" It should either update the text box to show the "Fixed Value to Variable" or it should show the "Variable to Variable" selected. -- 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, 6 months

2
6
0 / 0

[JBoss JIRA] Created: (JBDS-729) generate plugin dependencies in eclipse.ini/config.ini rather than hardcoding versions

by Nick Boldt (JIRA)

generate plugin dependencies in eclipse.ini/config.ini rather than hardcoding versions -------------------------------------------------------------------------------------- Key: JBDS-729 URL: https://jira.jboss.org/jira/browse/JBDS-729 Project: Developer Studio Issue Type: Bug Affects Versions: 2.0.1 Reporter: Nick Boldt Assignee: Denis Golovin >From Denis: > Bumped in JBDS launch problem, the reason is - migration to Eclipse 3.5 wasn't done for installer. Fixed for linux version, but need find a way to update original config.ini/eclipse.ini files during build adding xsl.transformation plug-ins in it without keeping a copies of ini files -- 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, 6 months

3
22
0 / 0

[JBoss JIRA] Created: (JBDS-1017) Deleted Server Runtimes appear in Seam Wizard

by Joshua Wulf (JIRA)

Deleted Server Runtimes appear in Seam Wizard --------------------------------------------- Key: JBDS-1017 URL: https://jira.jboss.org/jira/browse/JBDS-1017 Project: JBoss Developer Studio Issue Type: Bug Affects Versions: 3.0.0.M4, 3.0.0.CR1 Environment: Fedora 12 32-bit x86 Reporter: Joshua Wulf After deleting a server from the Servers or JBoss Server View window, that server's runtime still appears in the Seam Web Project wizard. This is persistent, even after JBDS / Eclipse is closed down and restarted. -- 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, 6 months

3
7
0 / 0

[JBoss JIRA] Created: (JBIDE-4985) New seam projects should configure hibernate tools with the DTP connection

by Max Rydahl Andersen (JIRA)

New seam projects should configure hibernate tools with the DTP connection -------------------------------------------------------------------------- Key: JBIDE-4985 URL: https://jira.jboss.org/jira/browse/JBIDE-4985 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Hibernate, Seam Reporter: Max Rydahl Andersen Assignee: Alexey Kazakov Fix For: 3.1.0.M4, 3.1.0.CR1 Now that hibernate console supports DTP connection profiles shouldn't we start using that for our Seam projects ? Removing the need to have connection info in the hibernate-console.properties ? (the other fields related to tx and others still need to there though) -- 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, 6 months

4
17
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues December 2009