You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Kent Tong <ke...@cpttm.org.mo> on 2005/10/02 04:31:34 UTC
Re: How to find location of a .page without the RequestCycle
Waluk, Michael <Michael.Waluk <at> workscape.com> writes:
> In my ServiceEncoder I'd like to assign a servletPath that mimics the actual
> page location under WEB-INF.
> For example, a link to the page located in
> /WEB-INF/comp/Home.page
> would get the servletPath
> /comp/Home.page (or whatever extension is assigned).
I may not be understanding your question. The full page path is availabe
in the "page" parameter:
http://localhost/myapp/app?service=page&page=comp/Home
So, your service encoder can easily convert it to:
http://localhost/myapp/comp/Home.page
However, this is already provided by the page-service-encoder coming
with Tapestry. So you probably don't need to write your own.
--
Author of a book for learning Tapestry (http://www.agileskills2.org/EWDT)
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org