Or have two instances of the same application with some configuration parameter to tell it which version it should be.
Norman Franke Answering Service for Directors, Inc. www.myasd.com <http://www.myasd.com/> > On Jul 30, 2015, at 4:12 PM, Thiago H de Paula Figueiredo > <thiag...@gmail.com> wrote: > > On Thu, 30 Jul 2015 16:19:50 -0300, Dimitris Zenios > <dimitris.zen...@gmail.com> wrote: > >> I would definitely split it into two web applications with a common >> tapestry module.Any other way will result to a mess. > > Agreed, as that's basically two distinct web applications which just happen > to be in the same server, even if they have shared code. > > If it was the same web application but with different domains and data, you > can use URL rewriting to make them work out of the same webapp instance. My > (incomplete, but working) Eloquentia blogging engine does that: > https://github.com/thiagohp/eloquentia. It can serve two or more different > blogs, each from its own different domain, in the same webapp instance. It > can also have subdomains for tags (domain.com for general stuff and > tapestry.domain.com for tapestry-specific posts, for example). > > -- > Thiago H. de Paula Figueiredo > Tapestry, Java and Hibernate consultant and developer > http://machina.com.br > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org >
