[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, 11 months
[JBoss JIRA] Created: (JBIDE-1338) Publish to server fails with unclear reason if server "Temporary Deploy Directory" is missing from the filesystem
by Marcus Adair (JIRA)
Publish to server fails with unclear reason if server "Temporary Deploy Directory" is missing from the filesystem
-----------------------------------------------------------------------------------------------------------------
Key: JBIDE-1338
URL: http://jira.jboss.com/jira/browse/JBIDE-1338
Project: JBoss Tools
Issue Type: Bug
Components: JBossAS
Affects Versions: 2.0.0.CR1
Environment: Windows XP, Red Hat Developer Studio, Seam 2.0
Reporter: Marcus Adair
It appears that when creating a new JBoss AS server instance in eclipse, JBoss Tools will create the needed temporary deploy directory for you.
If that directory later goes missing then publish will stop working and the error messages, while indicating a copy error, don't show what file path is really missing. A sample eclipse error show below is shown for each file that failed to deploy:
eclipse.buildId=unknown
java.version=1.6.0_03
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
Error
Mon Nov 19 11:59:58 MST 2007
Error copying file: C:\jboss-4.2.2.GA\server\default\deploy\spades-ear.ear\spades-ejb.jar\META-INF\e
jb-jar.xml to META-INF\ejb-jar.xml
java.io.IOException: The system cannot find the path specified
at java.io.WinNTFileSystem.createFileExclusively(Native Method)
at java.io.File.checkAndCreate(Unknown Source)
at java.io.File.createTempFile(Unknown Source)
at org.jboss.ide.eclipse.as.core.server.xpl.PublishUtil.copyFile(PublishUtil.java:98)
at org.jboss.ide.eclipse.as.core.server.xpl.PublishUtil.copyFile(PublishUtil.java:450)
at org.jboss.ide.eclipse.as.core.server.xpl.PublishUtil.copy(PublishUtil.java:505)
at org.jboss.ide.eclipse.as.core.server.xpl.PublishUtil.publishFull(PublishUtil.java:481)
at org.jboss.ide.eclipse.as.core.server.xpl.PublishUtil.copy(PublishUtil.java:496)
at org.jboss.ide.eclipse.as.core.server.xpl.PublishUtil.publishFull(PublishUtil.java:481)
at org.jboss.ide.eclipse.as.core.publishers.JstPublisher.fullPublish(JstPublisher.java:129)
at org.jboss.ide.eclipse.as.core.publishers.JstPublisher.publishModule(JstPublisher.java:111)
at org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.publishModule(DeployableSe
rverBehavior.java:130)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.j
ava:749)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.
java:835)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:66
9)
at org.eclipse.wst.server.core.internal.Server.doPublish(Server.java:887)
at org.eclipse.wst.server.core.internal.Server.publish(Server.java:874)
at org.eclipse.wst.server.core.internal.PublishServerJob.run(PublishServerJob.java:72)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Recreating the temporary directory resolves the problem. Presumably this could either be tested for during publish, or the directory could just be recreated since its temporary anyway.
--
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, 11 months