On Tue, May 08, 2007 at 11:08:29AM +0200, Christian Haselbach wrote: > LinkFactoryImpl seems to cache the context path from the first request. > This causes EngineServiceLink to have the context path of the first > request and not of the current request. > > Is there an easy way to have the current context path in > EngineServiceLink?
Oh, got that wrong. Tapestry uses the servlet path, not the context path, to create the url. However, regardless of that I need a mechanism to construct different urls for different requests. The request object is manipulated to reflect the true origin it comes from. Hence, the context path (or the servlet path) is set accordingly. But this does not work, because tapestry caches the servlet path, which is then used to create the url. Any ideas how to let Tapestry create the urls depending on the current context path? Thanks. Regards, Christian -- Christian Haselbach - [EMAIL PROTECTED] - +49 176 2082 5804 TNG Technology Consulting GmbH, Betastr. 13a, 85774 Unterföhring Geschäftsführer: Henrik Klagges, Gerhard Müller, Eike Reinel Amtsgericht München, HRB 135082 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
