I'll see if I can keep, but deprecate, the existing code. On Wed, Jun 2, 2010 at 10:53 AM, Thiago H. de Paula Figueiredo <thiag...@gmail.com> wrote: > On Wed, 02 Jun 2010 14:43:17 -0300, Christian Edward Gruber > <christianedwardgru...@gmail.com> wrote: > >> I realize that these are fairly intertwined in the code-base, but is there >> any way we can abstract these out into their own projects? It would be >> good, then, to be able to simply leave off the one you don't want, or keep >> both, but the mechanism would be external, and documented properly as a >> separate subsystem. Might make this sort of transition easier if it were >> first pulled out. > > As far as I can remember, the old URL rewriting code can be put in a > separate package without issues. > > -- > 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: dev-unsubscr...@tapestry.apache.org > For additional commands, e-mail: dev-h...@tapestry.apache.org > >
-- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org
