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]
