A servlet filter approach would mean that Portlet Tapestry would be significantly different from Servlet Tapestry (not that it isn't already the case).
On 4/11/06, James Carman <[EMAIL PROTECTED]> wrote: > The filter would basically have to do what the RequestCycleFactoryImpl class > does: > > WebRequest request = _infrastructure.getRequest(); > QueryParameterMap parameters = extractParameters(request); > decodeParameters(request.getActivationPath(), request.getPathInfo(), > parameters); > > After the parameters have been decoded, then it would try to lookup the > service name in the parameters. If the service name is not there, then I > guess it'd just let the request go on through (and not default to the "Home" > service). Otherwise, it'd just invoke the ServletRequestServicer, since it > knows that one of the services will take care of it. Sound about right to > you guys? > > -----Original Message----- > From: James Carman [mailto:[EMAIL PROTECTED] > Sent: Tuesday, April 11, 2006 12:37 PM > To: 'Tapestry development' > Subject: RE: [Discuss] Friendly URLs as the default > > If you just have the servlet filter take all URLs, then it can decide > whether to just handle the request itself or just let it go through to > whatever else might handle it (like the default servlet). > > -----Original Message----- > From: Howard Lewis Ship [mailto:[EMAIL PROTECTED] > Sent: Tuesday, April 11, 2006 11:37 AM > To: Tapestry development > Subject: Re: [Discuss] Friendly URLs as the default > > For Tapestry 5, I've been thinking in terms of three standard mappings: > > /asset/ > *.html > /action/ > > > Everything handled by the direct and external services and quite a bit > more, would fall under the /action/ pattern. > > I think your servlet filter idea has a lot of value as well. > > On 4/11/06, Massimo Lusetti <[EMAIL PROTECTED]> wrote: > > On 4/11/06, James Carman <[EMAIL PROTECTED]> wrote: > > > > > Unless we do what I suggested a while back and make Tapestry just a > servlet > > > filter mapped to "/*" and not an actual Servlet. That way, the URL > patterns > > > can be configured via HiveMind. > > > > I remember also someone wishing to show a proof of concept, does that > > gone forward? > > > > -- > > Massimo > > http://meridio.blogspot.com > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > Howard M. Lewis Ship > Independent J2EE / Open-Source Java Consultant > Creator, Jakarta Tapestry > Creator, Jakarta HiveMind > > Professional Tapestry training, mentoring, support > and project work. http://howardlewisship.com > > --------------------------------------------------------------------- > 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] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Howard M. Lewis Ship Independent J2EE / Open-Source Java Consultant Creator, Jakarta Tapestry Creator, Jakarta HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
