[jbosstools-issues] [JBoss JIRA] Commented: (JBDS-918) Studio does not start correctly afer VPE editor was opened in previous session

Johan Borchers (JIRA) jira-events at lists.jboss.org
Sun Nov 1 05:10:05 EST 2009


    [ https://jira.jboss.org/jira/browse/JBDS-918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12492452#action_12492452 ] 

Johan Borchers commented on JBDS-918:
-------------------------------------

Hello, 

I solved the XULRunner problem on the MAC OS X Snow Leopard by installing Mozilla XULRunner v1.9.1.3 from https://developer.mozilla.org/en/XULRunner. 
For the Mac XULRunner comes as an installer and installs itself in /Library/Frameworks/XUL.Framework. 
I did add a file in /private/etc/paths.d named XUL. This file contains 1 line text : /Library/Frameworks/XUL.framework/Versions/Current 
It adds /Library/Frameworks/XUL.framework/Versions/Current to the global PATH environment variable. 

After starting the 32 bit version of Eclipse Galileo SR1 in combination with the latest Visual Page Editor - for Richfaces, JSF and HTML / CSS 3.1.0.v200910281724M the error did not appear. The preview tab shows correctly. 

But after starting the 64 bit version of Eclipse Galileo SR1 in combination with the latest Visual Page Editor - for Richfaces, JSF and HTML / CSS 3.1.0.v200910281724M the error still appears. 

Johan

> Studio does not start correctly afer VPE editor was opened in previous session
> ------------------------------------------------------------------------------
>
>                 Key: JBDS-918
>                 URL: https://jira.jboss.org/jira/browse/JBDS-918
>             Project: JBoss Developer Studio
>          Issue Type: Bug
>          Components: visualeditor
>            Reporter: Daniel Azarov
>            Assignee: Yura Zhishko
>            Priority: Critical
>         Attachments: screenshot.png
>
>
> Testcase:
> 1. Open Studio with new workspace
> 2. Create jsf kick start project
> 3. Open WebContent/index.jsp
> 4. Close Studio
> 5. Open Studio again
> FAIL:
> org.eclipse.swt.SWTError: No more handles [Could not detect registered XULRunner to use]
> at org.eclipse.swt.SWT.error(SWT.java:3910)
> at org.eclipse.swt.browser.Mozilla.create(Mozilla.java:471)
> at org.eclipse.swt.browser.Browser.<init>(Browser.java:119)
> at org.jboss.tools.vpe.xulrunner.browser.XulRunnerBrowser.<init>(XulRunnerBrowser.java:87)
> at org.jboss.tools.vpe.xulrunner.editor.XulRunnerEditor.<init>(XulRunnerEditor.java:135)
> at org.jboss.tools.vpe.editor.mozilla.MozillaEditor$10.<init>(MozillaEditor.java:521)
> at org.jboss.tools.vpe.editor.mozilla.MozillaEditor.createPartControl(MozillaEditor.java:521)
> at org.jboss.tools.vpe.editor.VpeEditorPart.createVisualEditor(VpeEditorPart.java:911)
> at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditor.pageChange(JSPMultiPageEditor.java:210)
> at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditor.createPages(JSPMultiPageEditor.java:400)
> at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditorPart.createPartControl(JSPMultiPageEditorPart.java:125)
> at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:662)
> at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:462)
> at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:595)
> at org.eclipse.ui.internal.EditorAreaHelper.setVisibleEditor(EditorAreaHelper.java:271)
> at org.eclipse.ui.internal.EditorManager.setVisibleEditor(EditorManager.java:1417)
> at org.eclipse.ui.internal.EditorManager$5.runWithException(EditorManager.java:942)
> at org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(StartupThreading.java:31)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3855)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3476)
> at org.eclipse.ui.application.WorkbenchAdvisor.openWindows(WorkbenchAdvisor.java:803)
> at org.eclipse.ui.internal.Workbench$28.runWithException(Workbench.java:1384)
> at org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(StartupThreading.java:31)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3855)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3476)
> at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2316)
> 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(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: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

        


More information about the jbosstools-issues mailing list