tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Igor Drobiazko <igor.drobia...@gmail.com>
Subject Re: ComponentMessagesSource to become public API
Date Tue, 15 Dec 2009 07:21:52 GMT
After thinking about it once again I prefer this option too. It is more
convenient for a user to provide messages for a component in the catalog of
the containing page, inject the Messages service and bind it to component's
message parameter.

The default of the message parameter of a component is the injected Messages
service which represents the component's messages catalog.

On Sat, Dec 12, 2009 at 3:04 AM, Howard Lewis Ship <hlship@gmail.com> wrote:

> 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 <mlusetti@gmail.com>
> wrote:
> > On Wed, Dec 9, 2009 at 10:31 PM, Igor Drobiazko
> > <igor.drobiazko@gmail.com> 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: dev-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: dev-help@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
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>


-- 
Best regards,

Igor Drobiazko
http://tapestry5.de/blog

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message