I favor the option of extending the components with new parameters to specify the message catalog in which to look for messages, defaulting to searching their container's message catalog (as today). However, that logic is not centrally located I don't think.
On Fri, Dec 11, 2009 at 5:52 AM, Massimo Lusetti <[email protected]> wrote: > On Wed, Dec 9, 2009 at 10:31 PM, Igor Drobiazko > <[email protected]> wrote: > >> So, what is the consensus on this issue? > > My proposal is to let T5 traverse the component structure from inner > to outer most component and let the last matching win. > > This breaks existing behavior but i think that due to the current > nature of the message catalog (and the way it behave) there will be > not so many clients that will be broken since most of the use case are > messages-per-components. > Let's say now every component has only it own message catalog and it > will not suffer at all if T5 will search the components structure > upwards for overwrites. Doesn't? > > I think we could poll the user base for answers in this particular case. > > Cheers > -- > Massimo > http://meridio.blogspot.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- 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 --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
