[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-1658) Unable to select "Add JSF Capability" nor register new TLDs
Chris Simons (JIRA)
jira-events at lists.jboss.org
Fri Jan 25 10:34:21 EST 2008
[ http://jira.jboss.com/jira/browse/JBIDE-1658?page=comments#action_12396850 ]
Chris Simons commented on JBIDE-1658:
-------------------------------------
Max,
Sure - would you like that .zipped or in a .war?
I'll get something together and .zip it up unless I hear otherwise.
Thanks for your time.
> Unable to select "Add JSF Capability" nor register new TLDs
> -----------------------------------------------------------
>
> Key: JBIDE-1658
> URL: http://jira.jboss.com/jira/browse/JBIDE-1658
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JSF
> Affects Versions: 2.0.0.GA
> Environment: Windows XP SP2
> Eclipse Europa 3.3 with JBoss Tools 2.0GA
> Seam 2.0GA runtimes
> Using icefaces.tld v. 1.6.1
> Reporter: Chris Simons
> Assigned To: Viacheslav Kabanovich
> Priority: Optional
> Fix For: 2.1
>
> Attachments: no_jsf_capabilities.jpg
>
>
> Having trouble selecting "Add JSF Capability" on a project checked out through SVN that previously had the capability added by another user (on the same project/branch).
> All options under Project -> JBoss Tools are disabled except for "Add Struts Capability". [see screenshot]
> This prevents the registration of new TLDs, such as IceFaces, through the Pallette Library.
> I was able to successfully accomplish both of these tasks when I initially upgraded to JBoss Tools 2.0GA from Exadel Studio Pro. Now, it seems some settings under .settings is being loaded by other users trying to migrate to JBoss Tools/Eclipse and are now unable to add a new JSF capability, nor register any new TLDs.
> Also see the attached snippets from the eclipse log below:
> {code}
> eclipse.buildId=M20071023-1652
> java.version=1.6.0_02
> java.vendor=Sun Microsystems Inc.
> BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
> Command-line arguments: -os win32 -ws win32 -arch x86 -clean
> !ENTRY org.jboss.tools.vpe 4 0 2008-01-18 11:10:28.473
> !MESSAGE
> !STACK 0
> java.lang.NullPointerException
> at org.jboss.tools.jst.jsp.editor.TLDRegisterHelper.registerTld(TLDRegisterHelper.java:56)
> at org.jboss.tools.jst.jsp.editor.TLDRegisterHelper.registerTld(TLDRegisterHelper.java:39)
> at org.jboss.tools.vpe.editor.context.VpePageContext.registerTaglibs(VpePageContext.java:416)
> at org.jboss.tools.vpe.editor.context.VpePageContext.rebuildTaglibMap(VpePageContext.java:180)
> at org.jboss.tools.vpe.editor.context.VpePageContext.setTaglib(VpePageContext.java:155)
> at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addTaglib(VpeVisualDomBuilder.java:1912)
> at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createXmlns(VpeVisualDomBuilder.java:1868)
> at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:362)
> at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:221)
> at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:470)
> at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.buildDom(VpeVisualDomBuilder.java:192)
> at org.jboss.tools.vpe.editor.VpeController.init(VpeController.java:221)
> at org.jboss.tools.vpe.editor.VpeEditorPart$5.load(VpeEditorPart.java:512)
> at org.jboss.tools.vpe.editor.mozilla.MozillaEditor.onLoadWindow(MozillaEditor.java:461)
> at org.jboss.tools.vpe.editor.mozilla.MozillaEditor.access$1(MozillaEditor.java:456)
> at org.jboss.tools.vpe.editor.mozilla.MozillaEditor$4.onLoadWindow(MozillaEditor.java:217)
> at org.jboss.tools.vpe.xulrunner.browser.XulRunnerBrowser.onStateChange(XulRunnerBrowser.java:389)
> 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:597)
> 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)
> {code}
--
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
More information about the jbosstools-issues
mailing list