ingo schuster wrote:
>
> Hi,
>
> I found the root of our (/)images problem:
>
> The ECS layout uses a <base> tag, the JSP layout didn't. That's why
> "images/max.gif" worked well with ecs but not with JSPs (and why I used
> absolute links to the images). These absolute links are fine as long as you
> run jetspeed in the default web application "/", but they don't work with a
> own jetspeed application (e.g. "/jetspeed/"). That's how Mike seems to have
> his jetspeed configured.
> Anyway, not that the problem is clear, it's easy to fix: I changed all
> "/images" paths to "images" and I will add a <base> tag to the desfault.jsp.
>
You're right. Actually, I sent an email about this yesterday but it did not
seem to have reached the mailing-list for some reason, so here it is again:
Yes, I chenged the semantics of the images and external content links in the JR.p
and java code:
In the current version, the images/css etc are resolved like this in ECS:
http://<servername>:<serverport><contextname><content_root_url><image href>
is: the content_root is now relative to the webapp and default to "/"
and the <image_href> is relative to the content_root itself relative to
webapp.
This is handled in the ECS layout by adding a BASE html tag for resolving
relative URLs
<base href="http://<servername>:<severport><context>"/>
This should pretty easy to adapt the JSP layout.
If you have a better system for resolving all the URLs within the context
that would be definitely welcome.
--
Rapha�l Luta - [EMAIL PROTECTED]
Vivendi Universal Networks - Services Manager / Paris
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://marc.theaimsgroup.com/?l=jetspeed>
Problems?: [EMAIL PROTECTED]
