Raphael you perfectly understood my problem and i agree with your definitions:
1. "relative link" = "relative URI" = eg. <a href="page/default.psml"> 2. "asolute link" = "absolute URI" = eg. <a href="/jetspeed/portal/page/default.psml"> 3. "external link" = "absolute URL" = eg <a href="http://localhost:8080/jetspeed/portal/page/default.psml";>
Absolute links (ie number 2 above) should work OK and solve your issues
with
proxying but AFAIK they are not supported by the standard link clsses of Turbine 2.2
According to these definitions Turbine 2.2 class org.apache.turbine.util.RelativeDynamicURI produces absolute URIs and the class org.apache.turbine.util.DynamicURI produces absolute URLs. (isn't this naming a bit confusing?)
Jetspeed only uses DynamicURI (and hence absolute URLs) when I would expect it to use RelativeDynamicURI.
I'll admit not having having looked recently at those classes so if RelativeDynamic URI actually produces absolute URI, I agree it should become
the default behavior.
The only lost functionality I can see when swutching from DynamicURI to RelativeDynamicURI is that you're not able to use Turbine forced
redirection to SSL but that's not a big loss IMO.
Can you create a JIRA bug and attach a patch to the bug ? I'll make sure it goes into 1.6 if nobody else objects.
-- Raphael Luta - [EMAIL PROTECTED] Apache Jetspeed - Enterprise Portal in Java http://portals.apache.org/
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
