On Tue, 06 Dec 2011 08:28:02 -0200, Hugi Thordarson <h...@karlmenn.is>
wrote:
Good morning everyone.
Hi!
* About ~500 websites running in our CMS, each site a single web
application.
* In addition to the CMS, generic extensions that can be added
(Shopping, Event scheduling etc).
* Most sites include some custom components and logic.
All in all, a pretty typical setup for a CMS/Web Development shop.
So… Should I just declare the tapestry application package in the parent
project (the CMS itself) and then create components/pages/additional
services in that same package in my application project? Or do I have a
better way of modualrizing the systems? Should I do something like this
(http://tapestry.apache.org/component-libraries.html) for all the
applications and extensions?
The core application (CMS) would be a normal webapp and libraries for the
extensions and customizations. The key part here is using Tapestry-IoC.
You can easily override, decorate or advice the core services and add more
components, pages, mixins, dispatchers, request filters, etc in the
libraries for the customizations. I've done this in a personal project,
I've been working on large projects that use this approach and it works
very well.
--
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
