That's how I've done it in the past. With URL rewriting, this can be made even "nicer" in that you can map your more complicated url (with extra parameters/pathinfo) to a simpler url, and vice versa
Robert On Jul 23, 2010, at 7/2311:45 AM , Adam Zimowski wrote: > I was thinking about that Thiago :) In fact, that's about how we do it > currently with Struts. I'm going to give this a try today. > > Adam > > On Fri, Jul 23, 2010 at 11:37 AM, Thiago H. de Paula Figueiredo > <thiag...@gmail.com> wrote: >> On Fri, 23 Jul 2010 13:31:59 -0300, Adam Zimowski <zimowsk...@gmail.com> >> wrote: >> >>> I guess worst case scenario we can precompile these empty classes >>> during our publishing process. Need to verify if that will work but >>> that would be the work around. >> >> Why not having a single page class that loads the content to be rendered >> according to activation context or query parameters? >> >> -- >> Thiago H. de Paula Figueiredo >> Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and >> instructor >> Owner, Ars Machina Tecnologia da Informação Ltda. >> http://www.arsmachina.com.br >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org >> For additional commands, e-mail: users-h...@tapestry.apache.org >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
