[JBoss JIRA] Created: (JBIDE-1400) Eclipse plugin error
by George Lindholm (JIRA)
Eclipse plugin error
--------------------
Key: JBIDE-1400
URL: http://jira.jboss.com/jira/browse/JBIDE-1400
Project: JBoss Tools
Issue Type: Bug
Components: aop
Affects Versions: 2.0.0.CR1
Reporter: George Lindholm
Priority: Minor
No idea
-- Error Log --
Date: Fri Nov 30 18:14:24 PST 2007
Message: Could not acquire children from extension: org.jboss.tools.jst.web.ui.navigator.projectContent
Severity: Error
Plugin ID: org.eclipse.ui.navigator
Stack Trace:
java.lang.NullPointerException
at org.jboss.tools.jst.web.ui.navigator.XProjectContentProvider.getParent(XProjectContentProvider.java:56)
at org.eclipse.ui.internal.navigator.extensions.SafeDelegateTreeContentProvider.getParent(SafeDelegateTreeContentProvider.java:103)
at org.eclipse.ui.internal.navigator.NavigatorContentServiceContentProvider.getParent(NavigatorContentServiceContentProvider.java:480)
at org.eclipse.jface.viewers.AbstractTreeViewer.getParentElement(AbstractTreeViewer.java:1619)
at org.eclipse.jface.viewers.TreeViewer.getParentElement(TreeViewer.java:594)
at org.eclipse.jface.viewers.AbstractTreeViewer.internalExpand(AbstractTreeViewer.java:1546)
at org.eclipse.jface.viewers.AbstractTreeViewer.internalExpand(AbstractTreeViewer.java:1548)
at org.eclipse.jface.viewers.AbstractTreeViewer.internalExpand(AbstractTreeViewer.java:1548)
at org.eclipse.jface.viewers.AbstractTreeViewer.internalExpand(AbstractTreeViewer.java:1548)
at org.eclipse.jface.viewers.AbstractTreeViewer.internalExpand(AbstractTreeViewer.java:1548)
at org.eclipse.jface.viewers.AbstractTreeViewer.internalExpand(AbstractTreeViewer.java:1548)
at org.eclipse.jface.viewers.AbstractTreeViewer.setSelectionToWidget(AbstractTreeViewer.java:2393)
at org.eclipse.ui.navigator.CommonViewer.setSelectionToWidget(CommonViewer.java:337)
at org.eclipse.jface.viewers.StructuredViewer.setSelectionToWidget(StructuredViewer.java:1683)
at org.eclipse.jface.viewers.AbstractTreeViewer.setSelectionToWidget(AbstractTreeViewer.java:2783)
at org.eclipse.jface.viewers.StructuredViewer.setSelection(StructuredViewer.java:1639)
at org.eclipse.jface.viewers.TreeViewer.setSelection(TreeViewer.java:1095)
at org.eclipse.ui.navigator.CommonViewer.setSelection(CommonViewer.java:327)
at org.eclipse.ui.navigator.CommonNavigator.selectReveal(CommonNavigator.java:313)
at org.eclipse.ui.internal.navigator.actions.LinkEditorAction$3.run(LinkEditorAction.java:99)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
at org.eclipse.ui.internal.navigator.actions.LinkEditorAction$2.runInUIThread(LinkEditorAction.java:87)
at org.eclipse.ui.progress.UIJob$1.run(UIJob.java:94)
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:3296)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2974)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353)
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)
at org.eclipse.equinox.launcher.Main.main(Main.java:1148)
--
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
16 years, 5 months
[JBoss JIRA] Created: (JBIDE-1160) facelets template with css and subdirs do not render page in design and runtime
by Ronald van Kuijk (JIRA)
facelets template with css and subdirs do not render page in design and runtime
-------------------------------------------------------------------------------
Key: JBIDE-1160
URL: http://jira.jboss.com/jira/browse/JBIDE-1160
Project: JBoss Tools
Issue Type: Bug
Affects Versions: 2.0.0.Beta4
Environment: Windows 2000, jdk 1.5, eclipse 3.3
Reporter: Ronald van Kuijk
Priority: Minor
I have a (seam) project which uses facelets. The folder structure is like this:
root
|- layout
| |- template.xhtml
|- style
| |- style.css
|- folder1
| |- page1.1.xhtml
|- folder2
| |- page2.1.xhtml
|- home.xhtml
All pages reference this template in a ui:composition tag. The template contains a link to the css like
<link rel="stylesheet" type="text/css" media="all" href="/style/style.css" />
This way, all pages look good when designing them.
But when I publish my app on a none root folder in my appserver e.g. http://localhost:8080/myApp
none of the pages use the stylesheet. It is loaded from /style instead of /myApp/style
Using
<link rel="stylesheet" type="text/css" media="all" href="style/style.css" /> (no initial slash in the href)
only the homepage looks good in both design time and runtime
Getting all the pages working runtime, I changed the link to
<link rel="stylesheet" type="text/css" media="all" href="#{facesContext.externalContext.requestContextPath}/style/style.css" />
This works great in runtime, but makes designing the pages in the correct look and feel impossible.
It would be great if the designer could 'ignore' the #{facesContext.externalContext.requestContextPath} part of the href. so pages look good both design and runtime.
--
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
16 years, 5 months