Our app is brandable with the codebase being deployed to different environments, per business unit. So our common runtime will be packaged to ecommerce.jar, which will include service configuration (ejb definitions, etc), pages, etc... Then, when we configure website for company X, we will deploy the jar like any other lib, and intend on customizing the app by including stylesheets, property bundles, even page templates on its classpath to override ecommerce defaults, as desired.
This all works okay, with one limitations which we don't like, and that is that when it comes to overwriting resources from ecommerce.jar it's an all or nothing proposition. For example, if we have a product.tml and product.properties (with 100+ lines of message values inside) within ecommerce.jar, and all we want to overwrite is product.properties with two specific messages, Tapestry will not retain all the other messages. Is there a known solution to this? Currently, we see this as a maintenance problem in the long run, having to literally bring over a complete copy of message bundle from the common runtime just to customize one or two. Same thing goes for stylesheets and other resources. We would love Tapestry to work differently in this regard, and override individual bits from the file, not entire file. Adam --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
