tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Howard Lewis Ship <hls...@gmail.com>
Subject Re: T5: Howto implement your own Messages?
Date Wed, 02 Sep 2009 20:33:58 GMT
The right approach is to decorate or override Tapestry's
ComponentMessagesSource service ... unfortunately (I've done this for
a couple of customers) in 5.1 the implementation is tied pretty
heavily to some hard-to-test-or-replace internals.

On Wed, Sep 2, 2009 at 10:31 AM, Martin Reurings<martin@windgazer.nl> wrote:
> Hi All,
>
> I have, insucesfully been trying to intercept all calls to the MessagesImp
> from T5's core. For some reason, unknown to me, I have only been able to
> intercept the calls made to Messages begotten through @Inject, all messages
> called using ${message:....} in a .tml file are still routed directly to the
> T5 implementation, I have not yet gotten around to validation messages...
>
> I was hoping somebody out here has been trying to implement their own
> Messages implementation, or something of the sorts, and will be able to tell
> me how to do this. Seriously, something as simple as log.info(key) for every
> Message.get(String key) would be all that I need to keep going with what I'm
> doing, that is, as long as I can then implement whatever code I need instead
> of the log message ;).
>
> Cheers,
>
> Martin
>
> ---------------------------------------------------------------------
> 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!

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


Mime
View raw message