Absolute path doesn't matter. Dave is right. If you have your css
files under a protected path, you can't access them until you log in.
Here are a few suggestions.
In your security descriptor, use file extension matching rather than
path. Then, just don't match against 'css', 'jpg', and 'gif' files
(or 'png', 'jpeg', etc). If you don't match these file extensions,
you should be able to access them.
If you use path matching, specify the *other* paths in your app.
As for the css, if you pull your login page through the jsp compilier,
you do a hard include of the css file..
<style>
<%@ include file="/somepath/your.css"%>
</style>
On 10/5/06, Tom Innes <[EMAIL PROTECTED]> wrote:
Try
href="#{facesContext.externalContext.requestContextPath}/pages/css/styles.cs
This makes an absolute path to your style sheet.
Tom
-----Original Message-----
From: Brian Ehmann [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 04, 2006 10:42 PM
To: MyFaces Discussion
Subject: Help!! - html problems in jsf
I have a myfaces app that is going to the testers on monday and I
just ran into a snag, so ANY help would be much appreciated.
The app works great for all of the *.jsp pages. However I am using
container managed authentication on tomcat. When the user tries to
access any page before they are authenticated, they are forwarded to
a login.html page. The login functionality on the page works great,
however I can not get any of the images on that page to render and
the page does not find the css stylesheet. (this is what I get for
putting the eye-candy off until the last minute).
This is my first myfaces app so I've pretty much followed the
architecture in the Core JSF (by sun) and Java Server Faces (by
oreilly).
Does anyone have any ideas? I can send code and overall design if
needed but I can't figure out what I am missing here.
Thanks,
Brian
