[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, 6 months
[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, 6 months
[JBoss JIRA] Created: (JBDS-1781) All menus but one are missing on Ubuntu 11.04 (Unity)
by Fred Bricon (JIRA)
All menus but one are missing on Ubuntu 11.04 (Unity)
-----------------------------------------------------
Key: JBDS-1781
URL: https://issues.jboss.org/browse/JBDS-1781
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: runtime
Affects Versions: 4.1.0.CR3
Environment: Ubuntu 11.04 - Unity, jbdevstudio-product-linux-gtk-x86_64-4.1.0.v201107151650R-H633-CR3.jar
Reporter: Fred Bricon
Priority: Blocker
Attachments: jbds_4.1.CR3_missing_menus.jpg
After installing jbdevstudio-product-linux-gtk-x86_64-4.1.0.v201107151650R-H633-CR3.jar, it seems all menus but the "Window" one are missing.
I don't have the problem using a stock Helios JavaEE distro.
md5 checksum is ok.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 6 months
[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, 6 months
[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, 6 months
[JBoss JIRA] Created: (JBIDE-9383) Remove menu item "New Business Rule (using the guided editor)" from Drools Toolbar button menu.
by Vlado Pakan (JIRA)
Remove menu item "New Business Rule (using the guided editor)" from Drools Toolbar button menu.
-----------------------------------------------------------------------------------------------
Key: JBIDE-9383
URL: https://issues.jboss.org/browse/JBIDE-9383
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: drools
Affects Versions: 3.2.1.CR3
Environment: jbdevstudio-product-linux-gtk-4.1.0.v201107151650R-H633-CR3.
Reporter: Vlado Pakan
Assignee: Kris Verlaenen
Fix For: 3.2.1.Final
Attachments: DroolsMenuItemToRemove.png
This menu item has to be removed:
!DroolsMenuItemToRemove.png!
Guided Drools Rule Editor was removed from JBDS so also this menu item has to be removed from Drools Toolbar Menu because it's not running Guided Drools Rule Editor anymore. Eclipse text editor is run instead.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 6 months