Answering my own question. Not surpisingly the easiest solution turned out to be tweaking things at the Servlet API level... A simple filter that checks for weblogic header and decorates HttpServletRequest with a wrapper that supplies the right URL to Tapestry.
Andrus > I have a little unusual deployment situation with WebLogic 8./Tapesry > 3.0.3. Server admins configured Apache WL plugin that proxies all > requests to map URLs like "/somepath/myapp" to "/myapp" application > running on a WebLogic server. > > Still from the application point of view its context is "myapp" and it > is completely unaware of the "somepath" prefix - it doesn't show as > Context-Path or Request-URI. Examining the request I can see that the > only piece of information hinting to the full URL is a proprietary WL > header - WL-PATH-TRIM. Not surprisingly Tapestry knows nothing about. > :-( > > As a result all image and form URLs generated by Tapestry (that look > like "/myapp/xyz/something") are not valid in such environment (Apache > simply gives a 404). So I can load the front page of the application but > can't go anywhere after that. > > So I am wondering what my options are... Is there a way to switch all > internal asset (and Form!) links to use relative URLs? > > Thanks > Andrus > > > > > > --------------------------------------------------------------------- To > unsubscribe, e-mail: [EMAIL PROTECTED] For > additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
