...
Note that this applies to rewriting links generated by Tapestry too: a PageLink
to the urlrewritesuccess
page with an activation context of login
(path /urlrewritesuccess/login
) will generate an a
tag pointing to http://login.domain.com
.
The URLRewriteContext (added in 5.1.0.4) provides additional information for rewriting, particularly in the context of rewriting generated link urls. In the following example, we'll reconfigure the url used to render pages. Whereas the previous examples used separate rules for handling inbound and outbound rewriting, this demonstration will utilize a single rule for both scenarios. To simplify the example, we will assume that every page is named "XXXPage" (UserPage, TransactionPage, IndexPage, etc.). This naming convention also means that we don't have to worry about tapestry's auto-stripping of "index" from URLs, because our page would be IndexPage, rather than Index.
...
Note that getPageParameters()
will only return non-null when process
is called due to page link creation, and getComponentEventParameters()
will only return non-null when process
is called as a result of creating component event links.
Scrollbar |
---|