Thanks Raphael for your quick reply. I understand your instructions about how to customize the $link behaviour.
The other option, as far as i understand, is setting the tomcat ServerHost name (which is not addressable on the internet) to something that resolves on the firewall machine so that these requests can be forwarded to the tomcat server. Is this right?
Yes. Have your ServerHost resolve to an internal IP within your network and the same hostname resolve to the pulic IP of your proxy on the Internet.
At this stage I'm not interested in running the stock code, I'm interested in having Jetspeed links addressable on the internet if my tomcat server is on a private IP behind a Firewall/Proxy.
Be prepared to thoroughly check your webapp as Turbine and relative links
don't
work necessarily very well since the request path is hardly predictable
Why you say that the request path is hardly predictable? Is there any specific reason why absolute urls are preferable?
It all depends what you call "absolute" vs "relative".
My personal 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";>
WHat bothers you seems to be the use of external links (ie abolute URLs). What doesn't work well in Jetspeed are the relative links because Turbine encodes the request parameters within the request paths and since you never know how many parameters you may have in your request path.
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
-- 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]
