3:55 p.m.
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
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
3:57 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-1658) Unable to select "Add JSF Capability" nor register new TLDs
[ http://jira.jboss.com/jira/browse/JBIDE-1658?page=all ]
Chris Simons updated JBIDE-1658:
--------------------------------
Attachment: no_jsf_capabilities.jpg
Screenshot showing JBoss Tools option list under project properties on project checked out
from SVN.
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
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
4:03 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-1658) Unable to select "Add JSF Capability" nor register new TLDs
[ http://jira.jboss.com/jira/browse/JBIDE-1658?page=comments#action_12395827 ]
Max Andersen commented on JBIDE-1658:
-------------------------------------
and isn't this just because the jsf capabilities is *already* in there or ?
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
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
5:16 a.m.
New subject: [JBoss JIRA] Assigned: (JBIDE-1658) Unable to select "Add JSF Capability" nor register new TLDs
[ http://jira.jboss.com/jira/browse/JBIDE-1658?page=all ]
Alexey Kazakov reassigned JBIDE-1658:
-------------------------------------
Assignee: Viacheslav Kabanovich
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
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
5:13 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-1658) Unable to select "Add JSF Capability" nor register new TLDs
[ http://jira.jboss.com/jira/browse/JBIDE-1658?page=all ]
Max Andersen updated JBIDE-1658:
--------------------------------
Fix Version/s: 2.1
Priority: Optional (was: Major)
chris - could you supply a minimal test project that had this error ? We can't
reproduce it otherwise.
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
9:34 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-1658) Unable to select "Add JSF Capability" nor register new TLDs
[ 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
10:29 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-1658) Unable to select "Add JSF Capability" nor register new TLDs
[ http://jira.jboss.com/jira/browse/JBIDE-1658?page=comments#action_12396877 ]
Max Andersen commented on JBIDE-1658:
-------------------------------------
we will need the actual eclipse project that is causing the problem, put in a zip for
compresion - the .war is irrelevant.
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
8:58 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-1658) Unable to select "Add JSF Capability" nor register new TLDs
[ http://jira.jboss.com/jira/browse/JBIDE-1658?page=comments#action_12397356 ]
Chris Simons commented on JBIDE-1658:
-------------------------------------
When you pointed to the .settings directory, it reminded me that I had always wondered if
this was the problem.
Let me run down the steps I did to fix this issue (it also, coincidentally, fixed another
bug that I had entered into JIRA, I will put these same comments there, too)...
I found that my /project/.settings/org.jboss.tools.jst.web.xml was *missing*.
I copied this file from a test project called "jsfpallete" and let Eclipse
injest it. I then closed Eclipse and the program added a bunch of additional libraries to
the file akin to my project (JBoss Seam, IceFaces, etc.). I made a few adjustments to the
file, specifically:
From:
<FILESYSTEMS APPLICATION_NAME="feature-pm" ENTITY="FileSystems"
VERSION="2.0.0.cr1" WORKSPACE_HOME="./WebContent/WEB-INF">
To:
<FILESYSTEMS APPLICATION_NAME="feature-pm" ENTITY="FileSystems"
VERSION="2.0.0.cr1" WORKSPACE_HOME="./view/WEB-INF">
Because we had started our Seam project prior to JBoss Tools, we did not have the
pre-designated "WebContent" directory and instead had our WEB-INF under a folder
called /view. Believe it or not, this totally fixed the issue. I can now add the IceFaces
TLD and get content assist *and* add XHTML and other files to the project.
However, I am worried that as we check out additional projects from SVN, we are going to
have to go through this same routine each time. Do you all have any thoughts on why this
may have happened in the first place?
Thanks for your amazing support. If you feel this is something that can be addressed via
an update, please by all means do - it would certainly alleviate some confusion.
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
11:10 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-1658) Unable to select "Add JSF Capability" nor register new TLDs
[ http://jira.jboss.com/jira/browse/JBIDE-1658?page=comments#action_12397396 ]
Viacheslav Kabanovich commented on JBIDE-1658:
----------------------------------------------
Please see my comment to JBIDE-1655, these issues are related.
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
8:18 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-1658) Unable to select "Add JSF Capability" nor register new TLDs
[ http://jira.jboss.com/jira/browse/JBIDE-1658?page=all ]
Viacheslav Kabanovich updated JBIDE-1658:
-----------------------------------------
Fix Version/s: 2.0.1
(was: 2.1)
Will be fixed together with JBIDE-1655.
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.0.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
8:19 a.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-1658) Unable to select "Add JSF Capability" nor register new TLDs
[ http://jira.jboss.com/jira/browse/JBIDE-1658?page=all ]
Viacheslav Kabanovich resolved JBIDE-1658.
------------------------------------------
Resolution: Done
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.0.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
6665
days inactive
6678
days old
jbosstools-issues@lists.jboss.org
10 comments
4 participants
participants (4)
-
Alexey Kazakov (JIRA) -
Chris Simons (JIRA)
-
Max Andersen (JIRA)
-
Viacheslav Kabanovich (JIRA)