I was wondering why Jetspeed builds absolute URLs instead of relative urls when building links to panes, portlets, etc..
I find out that Jetspeed builds its URLs using classes like org.apache.jetspeed.util.template.JetspeedLink which use the turbine class org.apache.turbine.util.DynamicURI that builds absolute URls. Turbine also include a class org.apache.turbine.util.RelativeDynamicURI which extends DynamicURI and returns relative URLs. The problem is that Jetspeed (v. 1.5) never uses RelativeDynamicURI to builds its own links. Is there any reason for that? I need Jetspeed to produce relative urls because my server stands behind a firewall/proxy and it's not directly accessable from the internet hence absolute urls are unusable. To let jetspeed produce relative URLs I had to implement an hack into the turbine DynamicURI source code changing the behaviour of the metoth toString so that it doens't include protocol, server name and port. Is tehre any better way to do this ? Any of you managed to run Jetspped behind a firewall/proxy? Carlo --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
