Darren Gilroy wrote: > I am not sure how a relative url within a turbine app can be defined other than the possibilities of
1. not including the host:port 2. also not including the context/servlet There is a RelativeTemplateLink class in turbine that implements (1). It's implementation is slightly different in t2 vs. t3. In t3 DynamicURI can be set to include/exclude the host:port info and the TemplateLink can work with this to generate absolute or type (1) urls. In t2 there are separate classes for the absolute and relative urls. t2's method does not allow the same link tool to be used in an template for generating an email and also to generate relative url's in the webapp. I recommend subclassing DynamicURI and overriding its toString() method to give you what you need. And then write a link tool that wraps it. The current classes should be a pretty good guide. john mcnally > Hi - > > I'm trying to place my turbine application behind an apache (1.3) proxy, and > I need some help. > > I have /app proxied to anotherhost:8180/myapp/servlet/myapp via ProxyPass, > with ProxyPassReverse working too, but I need some help with the next step. > > The $link object (org.apache.turbine.util.template.TemplateLink) and the > $content object both return fully-qualified urls. I would like to adjust > those urls so they don't include the /myapp/servlet/mayapp part, or, > preferably, have those objects return relative URLs. > > Ideas, suggestions, how-tos for this next step? > > Thanks! > -best-darr- > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
