June 2011 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-8225) Richfaces component installed on Eclipse SDK is not fully functional

by Denis Golovin (JIRA)

Richfaces component installed on Eclipse SDK is not fully functional -------------------------------------------------------------------- Key: JBIDE-8225 URL: https://issues.jboss.org/browse/JBIDE-8225 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Affects Versions: 3.2.0.CR1 Reporter: Denis Golovin Assignee: Alexey Kazakov Priority: Critical -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

3
9
0 / 0

[JBoss JIRA] Created: (JBIDE-8150) XPCOM error during browsing on welcome page on Fedora 64b

by Jiri Peterka (JIRA)

XPCOM error during browsing on welcome page on Fedora 64b --------------------------------------------------------- Key: JBIDE-8150 URL: https://issues.jboss.org/browse/JBIDE-8150 Project: Tools (JBoss Tools) Issue Type: Bug Components: core Affects Versions: 3.2.0.Beta2 Environment: JBDS 4.0.0.CR1 H65, Linux 64 (Fedora 14 - 2.6.35.10-74.fc14.x86_64) Reporter: Jiri Peterka During Browsing on Welcome page XPCOM error occured: org.eclipse.swt.SWTError: XPCOM error -2147467262 at org.eclipse.swt.browser.Mozilla.error(Mozilla.java:2414) at org.eclipse.swt.browser.Mozilla.OnStateChange(Mozilla.java:3346) at org.eclipse.swt.browser.Mozilla$10.method3(Mozilla.java:986) at org.eclipse.swt.internal.mozilla.XPCOMObject.callback3(XPCOMObject.java:266) at org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method) at org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:2229) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3159) 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(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:619) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574) at org.eclipse.equinox.launcher.Main.run(Main.java:1407) at org.eclipse.equinox.launcher.Main.main(Main.java:1383) org.eclipse.swt.SWTError: XPCOM error -2147467259 at org.eclipse.swt.browser.Mozilla.error(Mozilla.java:2414) at org.eclipse.swt.browser.Mozilla.onDispose(Mozilla.java:2429) at org.eclipse.swt.browser.Mozilla$5.handleEvent(Mozilla.java:891) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1282) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1263) at org.eclipse.swt.widgets.Widget.release(Widget.java:1080) at org.eclipse.swt.widgets.Control.release(Control.java:3304) at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:1293) at org.eclipse.swt.widgets.Widget.release(Widget.java:1083) at org.eclipse.swt.widgets.Control.release(Control.java:3304) at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:1293) at org.eclipse.swt.widgets.Widget.release(Widget.java:1083) at org.eclipse.swt.widgets.Control.release(Control.java:3304) at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:1293) at org.eclipse.swt.widgets.Widget.release(Widget.java:1083) at org.eclipse.swt.widgets.Control.release(Control.java:3304) at org.eclipse.swt.widgets.Widget.dispose(Widget.java:462) at org.eclipse.ui.internal.PartPane.dispose(PartPane.java:180) at org.eclipse.ui.internal.ViewPane.dispose(ViewPane.java:193) at org.eclipse.ui.internal.WorkbenchPartReference.dispose(WorkbenchPartReference.java:681) at org.eclipse.ui.internal.WorkbenchPage.disposePart(WorkbenchPage.java:1721) at org.eclipse.ui.internal.WorkbenchPage.partRemoved(WorkbenchPage.java:1713) at org.eclipse.ui.internal.ViewFactory.releaseView(ViewFactory.java:257) at org.eclipse.ui.internal.Perspective.hideView(Perspective.java:606) at org.eclipse.ui.internal.WorkbenchPage.hideView(WorkbenchPage.java:2387) at org.eclipse.ui.internal.ViewPane.doHide(ViewPane.java:213) at org.eclipse.ui.internal.PartStack.close(PartStack.java:541) at org.eclipse.ui.internal.PartStack.close(PartStack.java:524) at org.eclipse.ui.internal.PartStack$1.close(PartStack.java:120) at org.eclipse.ui.internal.presentations.util.TabbedStackPresentation$1.handleEvent(TabbedStackPresentation.java:83) at org.eclipse.ui.internal.presentations.util.AbstractTabFolder.fireEvent(AbstractTabFolder.java:269) at org.eclipse.ui.internal.presentations.util.AbstractTabFolder.fireEvent(AbstractTabFolder.java:278) 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:71) at org.eclipse.ui.internal.presentations.PaneFolder.notifyCloseListeners(PaneFolder.java:631) at org.eclipse.ui.internal.presentations.PaneFolder$3.close(PaneFolder.java:206) at org.eclipse.swt.custom.CTabFolder.onMouse(CTabFolder.java:1595) at org.eclipse.swt.custom.CTabFolder$1.handleEvent(CTabFolder.java:261) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3540) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3161) 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(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:619) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574) at org.eclipse.equinox.launcher.Main.run(Main.java:1407) at org.eclipse.equinox.launcher.Main.main(Main.java:1383) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

5
16
0 / 0

[JBoss JIRA] Created: (JBDS-1698) Weak Modeshape Performance

by Pavol Srna (JIRA)

Weak Modeshape Performance -------------------------- Key: JBDS-1698 URL: https://issues.jboss.org/browse/JBDS-1698 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: Modeshape Affects Versions: 5.0.0.M2 Reporter: Pavol Srna Fix For: 5.0.0.M3 1) Import Parts Model Project Set Example (Help -> Project Examples... -> Teiid Designer -> ..) 2) Right click on PartsProject and select ModeShape -> Publish The ModeShape publish dialog appears on the screen after more then 2 minutes. On the first look it seems like frozen, but after cca 2 minutes starts everything to work. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

8
11
0 / 0

[JBoss JIRA] Created: (JBIDE-1273) When hot code replace fails, offer "restart deployment "as an alternative

by Gavin King (JIRA)

When hot code replace fails, offer "restart deployment "as an alternative ------------------------------------------------------------------------- Key: JBIDE-1273 URL: http://jira.jboss.com/jira/browse/JBIDE-1273 Project: JBoss Tools Issue Type: Feature Request Reporter: Gavin King The dialog box t hat eclipse pops up when hot code replace fails is very irritating, but it would be less irritating if it offered "restart deployment" as an alternative. Actually it should be smart enough to NOT pop this dialog at all for classes in src/action. So I think the Seam tools need to hijack this whole feature of eclipse. -- 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

14 years, 8 months

4
9
0 / 0

[JBoss JIRA] Created: (JBDS-1662) Cannot deploy Seam Portlet Example to JBoss EPP 4.3

by Pavol Srna (JIRA)

Cannot deploy Seam Portlet Example to JBoss EPP 4.3 --------------------------------------------------- Key: JBDS-1662 URL: https://issues.jboss.org/browse/JBDS-1662 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Affects Versions: 4.1.0.M1 Reporter: Pavol Srna Attachments: server.log See log attached. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

13
37
0 / 0

[JBoss JIRA] Created: (JBIDE-8427) Really slow deployment while dialog visible

by henk de boer (JIRA)

Really slow deployment while dialog visible ------------------------------------------- Key: JBIDE-8427 URL: https://issues.jboss.org/browse/JBIDE-8427 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.2.0.CR1 Environment: Mac OS X 10.6.4, Eclipse 3.6.1 (64 bits) Reporter: henk de boer When a project is deployed using the Jboss tools WTP adapter with the progress dialog visible the operation is really slow. As soon as the operation is send to the background it's fast again. It seems the code tries to display every file name on screen, which results in a maximum copy rate of 60 files/second (screen refresh). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

7
14
0 / 0

[JBoss JIRA] Created: (JBIDE-9223) Move jaxrs wizards to jaxrs?

by Max Rydahl Andersen (JIRA)

Move jaxrs wizards to jaxrs? ---------------------------- Key: JBIDE-9223 URL: https://issues.jboss.org/browse/JBIDE-9223 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Reporter: Max Rydahl Andersen Assignee: Brian Fitzpatrick Priority: Critical Fix For: 3.3.0.M3 looking at JBIDE-9220 mentioning creation jaxrs service without enablement of jaxrs - should we move the jaxrs wizard to jaxrs or is it best kept in ws still ? about autoenablement then I'm not sure - comments/feedback welcome. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-8919) Recognize and define ESB Runtime from SOA-P product

by Vlado Pakan (JIRA)

Recognize and define ESB Runtime from SOA-P product --------------------------------------------------- Key: JBIDE-8919 URL: https://issues.jboss.org/browse/JBIDE-8919 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: runtimes Affects Versions: 3.2.1.M1 Reporter: Vlado Pakan Assignee: Snjezana Peco When searching for runtimes (Menu Window > Preferences > JBoss Tools > JBoss Tools Runtimes) SOA-P is properly recognized as SOA-P Runtime but contained ESB Runtime is not added to defined ESB Runtimes. Doesn't work with these SOA-P versions 5.0.2, 5.1.0, 4.3.CP.04. JBT should automatically detect ESB Runtime within SOA-P product and define it for later use. Has to be working also with SOA-P Standalone products. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

8
21
0 / 0

[JBoss JIRA] Created: (JBDS-1655) Recognize and define Drools Runtime from SOA-P standalone product during installation

by Vlado Pakan (JIRA)

Recognize and define Drools Runtime from SOA-P standalone product during installation ------------------------------------------------------------------------------------- Key: JBDS-1655 URL: https://issues.jboss.org/browse/JBDS-1655 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Affects Versions: 4.1.0.M1 Reporter: Vlado Pakan When searching for runtimes during installation SOA-P is properly recognized as SOA-P Runtime but contained ESB Runtime is not added to defined ESB Runtimes when installed JBDS is run. Doesn't work with these SOA-P versions 5.0.2, 5.1.0, 4.3.CP.04. JDBS should automatically detect ESB Runtime within SOA-P product during installation and define it for later use. Has to be working also with SOA-P Standalone products. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

10
15
0 / 0

[JBoss JIRA] Created: (JBIDE-3113) Consolidation/clean up of preference pages

by John Graham (JIRA)

Consolidation/clean up of preference pages ------------------------------------------ Key: JBIDE-3113 URL: https://jira.jboss.org/jira/browse/JBIDE-3113 Project: Tools (JBoss Tools) Issue Type: Bug Components: common, drools, jbpm Affects Versions: 3.0.0.cr1 Environment: JBossTools-3.0.0.CR1-N200811050757-ALL-linux-gtk Reporter: John Graham Priority: Minor JBT currently has three preference page categories: 1. Drools 2. JBoss jBPM 3. JBoss Tools The first two should be listed as subsections of the JBoss Tools category. Alternatively, I suggest that the top level category should just be JBoss: - JBoss -- Drools -- jBPM Also, the JBoss Tools and JBoss jBPM top level pages in each of these categories do not expose preferences, but rather the default buttons or simply a label ("JBoss Tools"). These top level pages should show overall JBT preferences. See the Java preferences or other examples in the Eclipse platform for this idea. (Also note that the DTP 1.6.x way of doing this is wrong... ;) ) -- 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, 8 months

6
19
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 June 2011