Tapestry 5.3 introduces the idea of skinning: its broken up into a couple of parts.
One part is looking at the request to determine the "axes" (plural of axis) of customization. In your case, one axis would be locale (which is built into Tapestry). The other axis would be based on tenant, which you should be able to determine from the request, based on the host name in the request. Once you have that, you can define rules for mapping a base Resource to a skinned version of a Resource; the built-in Tapestry code for this adds suffixes to the base file name to identify the locale. I would typically use a sub-folder based on (in your example tenant, then use the standard localization there (since that's built directly into the Resource API). http://tapestry.apache.org/5.3/apidocs/org/apache/tapestry5/services/pageload/ComponentResourceSelector.html http://tapestry.apache.org/5.3/apidocs/org/apache/tapestry5/services/pageload/ComponentRequestSelectorAnalyzer.html On Wed, Dec 19, 2012 at 9:05 AM, Thiago H de Paula Figueiredo < thiag...@gmail.com> wrote: > On Wed, 19 Dec 2012 14:33:55 -0200, nquirynen <nat...@pensionarchitects.be> > wrote: > > Maybe you can make an implementation of AssetSource >> > > Better yet, an AssetFactory. Take a look in the Tapestry sources of > ClasspathAssetFactory and ContextAssetFactory. > > -- > Thiago H. de Paula Figueiredo > > > ------------------------------**------------------------------**--------- > To unsubscribe, e-mail: > users-unsubscribe@tapestry.**apache.org<users-unsubscr...@tapestry.apache.org> > For additional commands, e-mail: users-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
