Most of that is already there; however, there probably needs to be other work to ensure that Tapestry generates the correct URL; right now it includes the context part and the path from there; the servlet needs to be injected into the middle of that.
On Sun, May 4, 2008 at 2:50 AM, ice96 <[EMAIL PROTECTED]> wrote: > > As I understand, to make Tapestry more friendly with integration we need to > write a little chainge tappestry TapestryFilter: > 1) Take out from TapestryFilter to more reusable class. Lets say > TapestryInit > 2) Create class TapestryServlet which uses TapestryInit > 3) Rewrite TapestryFilter to use TapestryInit > Am I right? > -- > View this message in context: > http://www.nabble.com/groovy-grails-and-tapestry-5-integration-experiments-tp17035475p17044538.html > > > Sent from the Tapestry - Dev mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Howard M. Lewis Ship Creator Apache Tapestry and Apache HiveMind --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
