The ComponentRequestHandler pipeline (new in 5.1) is for this purpose. You can contribute a ComponentRequestFilter; your filter is passed all the details of the request (page names, nested ids, page activation context, event context) and can decide how to proceed.
CRH pipeline is a facade around two different pipelines: ComponentEventRequestHandler and PageRenderRequestHandler. In some cases, you may want to contribute a filter to once of those pipelines instead. On Thu, Feb 5, 2009 at 12:51 PM, Thiago H. de Paula Figueiredo <thiag...@gmail.com> wrote: > Em Thu, 05 Feb 2009 15:20:02 -0300, Jonathan O'Connor <ninki...@eircom.net> > escreveu: > >> Thiago, > > Hi! > >> I thought about the service idea, but what would it look like? >> Class extractPageClass(String requestPath) would be what I'd want. > > That's what I want too. I would add a String extractPageName(String > requestPath), returning the Tapestry page name (something like > admin/user/edit). > >> However, for each Dispatcher, you'd want a PageClassExtracter as well, and >> I'm sure there'd be lots of duplication. > > I haven't thought of the dispatcher issue yet, but maybe we could suppose > that our new service would deal only with normally-dispatched requests. > > -- > Thiago H. de Paula Figueiredo > Independent Java consultant, developer, and instructor > http://www.arsmachina.com.br/thiago > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- Howard M. Lewis Ship Creator Apache Tapestry and Apache HiveMind --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
