... in the meantime I found this interesting posting which goes in the same
direction:
http://old.nabble.com/-T5--How-to-%22skin%22-.properties-files--Localization-almost-good...-tp15843698p15845508.html
--
View this message in context:
http://old.nabble.com/-T5--Best-practices-for-customer-spe
Thanks for your valuable input. I really appreciate it.
Just to clarify: I am talking about different deployments for each of the
customers. I was thinking of setting the LANG=de_DE_ in the
environment and having a service evaluate that.
Lothar
Josh Canfield wrote:
>
>> I am using Tapestry i
> I am using Tapestry in a product that will be used by multiple customers.
The approaches you've listed require you to modify the source code in
order to scale up the supported customers. If you want to add
customers to the application without modifying code then I'd change to
test for specific o
I recommend you to check the way the BeanEditForm Works. U might
dynamically use a strategy to create the beanModels for a specific
form. Even if this doesn't apply directly u can get very good ideas
from the source code of the BeanEditForm
On Tue, Jul 6, 2010 at 11:27 AM, t5_lothar wrote:
>
> Hi
On Tue, 06 Jul 2010 06:27:41 -0300, t5_lothar wrote:
Hi all,
Hi!
(1) If/Else approch: ... display some fields ...
... display other fields ...
1) Never use expansions in parameters. It coerces the value to a String.
2) This approach tends to get unmaintainable in the long run.
(2) C
