Em Mon, 30 Mar 2009 19:28:23 -0300, xfile80303 <l...@grokers.net> escreveu:
> http://myhost.com/SITE/page/params
>
> Where the only difference from normal Tapestry URL is the insertion of
> the SITE before the rest of the URI, such that SITE could be anything
> (like, "partner", "foo", or "main" etc.).
>
> So the URL Rewriting implementation does not seem to be quite a match
> since if I insert anything for SITE, as mentioned, it breaks Tapestry's
> ability to properly deal with the request for pages and page content,
Have you tested this? I don't think it will break Tapestry, as it would
only see requests for http://myhost.com/page/params.
Yes, I have, but I was inserting the SITE value into the request URL which is
what does the breaking.
> etc. The SITE parameter needs to be "virtual" and yet still generated
> for page links.
The URL rewriting support also rewrites generated links, so all you need
here is to implement a rule that does rewrites incoming URLs to remove the
site id and rewrites generated links to include the site id. I wrote the
URL writing support a little more complicated scenario: login.domain.com
to domain.com/page/domain and vice-versa.
Okay this sounds like a plausible approach, but I'm confused about how I would
identify the fact that my filter is being called to handle an incoming request
(and remove the SITE) or a link generation request (and insert the site).
Levi
--
View this message in context:
http://n2.nabble.com/T5.1-URL-Rewriting-tp2557652p2560110.html
Sent from the Tapestry Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
