[
http://jira.jboss.com/jira/browse/JBIDE-1083?page=comments#action_12389505 ]
Reiner Kappenberger commented on JBIDE-1083:
--------------------------------------------
I'm experiencing the same problem quite frequently. Whenever I set up a facelets
project and edit an xhtml file with JBossIDE it simply hangs up when editing the file
(Eclipse x86, JDK 1.5.0_11 (32bit)).
I will try to provide an file (or project) that causes the hang when I have time.
RHDS crashes when editing in XHTML (facelet) file
-------------------------------------------------
Key: JBIDE-1083
URL:
http://jira.jboss.com/jira/browse/JBIDE-1083
Project: JBoss Tools
Issue Type: Bug
Components: Visual Page Editor, jsp/jsf/xml source editing
Affects Versions: 2.0.0.Beta4
Environment: RHDS Beta 2, Facelets 1.1.12, Trinidad 1.2.3, RichFaces 3.1.1GA
Reporter: Wolfgang Chico Toepfer
Assigned To: Sergey Vasilyev
Priority: Critical
Fix For: 2.0.1
While editing in an XHTML (facelet) file the system reaches a NullPointerException, then
the whole IDE stall and it remains for you to quite task-manager-wise..
Here is the latest log (the whole thing is repeatable as you like, but I uninstalled RHDS
Beta 2 and reverted to Beta 1, now everything's fine ;):
!ENTRY org.jboss.tools.vpe 4 0 2007-10-15 08:15:45.671
!MESSAGE
!STACK 0
java.lang.NullPointerException
at
org.jboss.tools.jst.jsp.editor.TLDRegisterHelper.registerTld(TLDRegisterHelper.java:54)
at
org.jboss.tools.jst.jsp.editor.TLDRegisterHelper.registerTld(TLDRegisterHelper.java:38)
at
org.jboss.tools.vpe.editor.context.VpePageContext.registerTaglibs(VpePageContext.java:415)
at
org.jboss.tools.vpe.editor.context.VpePageContext.rebuildTaglibMap(VpePageContext.java:179)
at org.jboss.tools.vpe.editor.context.VpePageContext.setTaglib(VpePageContext.java:154)
at
org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addTaglib(VpeVisualDomBuilder.java:1716)
at
org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createXmlns(VpeVisualDomBuilder.java:1679)
at
org.jboss.tools.vpe.editor.VpePreviewDomBuilder.createNode(VpePreviewDomBuilder.java:71)
at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:229)
at
org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:457)
at
org.jboss.tools.vpe.editor.VpeVisualDomBuilder.buildDom(VpeVisualDomBuilder.java:198)
at org.jboss.tools.vpe.editor.mozilla.MozillaPreview.buildDom(MozillaPreview.java:464)
at org.jboss.tools.vpe.editor.VpeEditorPart$6.load(VpeEditorPart.java:512)
at
org.jboss.tools.vpe.editor.mozilla.MozillaPreview.onLoadWindow(MozillaPreview.java:357)
at org.jboss.tools.vpe.editor.mozilla.MozillaPreview.access$0(MozillaPreview.java:352)
at
org.jboss.tools.vpe.editor.mozilla.MozillaPreview$1.onLoadWindow(MozillaPreview.java:132)
at
org.jboss.tools.vpe.mozilla.browser.MozillaBrowser.OnStateChange(MozillaBrowser.java:1812)
at
org.jboss.tools.vpe.mozilla.browser.MozillaBrowser$4.method3(MozillaBrowser.java:777)
at
org.jboss.tools.vpe.mozilla.internal.swt.xpl.XPCOMObject.callback3(XPCOMObject.java:263)
at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method)
at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2265)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3291)
at org.eclipse.ui.application.WorkbenchAdvisor.openWindows(WorkbenchAdvisor.java:801)
at org.eclipse.ui.internal.Workbench$25.runWithException(Workbench.java:1342)
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:123)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3659)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3296)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2309)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219)
at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at
org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:169)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176)
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:508)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:447)
at org.eclipse.equinox.launcher.Main.run(Main.java:1173)
What is also worthnoting:
1) the Content assist does not work amymore with the Trinidad lib (tr and trh)
2) so I added the TLDs of Trinidad to the JBOSS Tools pane by drag and drop to that pane,
which worked
--
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