Hi,
In 5.3, overriding ComponentMessageSource is a bit harder than you might think:
https://issues.apache.org/jira/browse/TAP5-1850
Luke
On 12 Apr 2012, at 10:11, Gerold Glaser wrote:
> Hi Henrik!
>
> You can override or decorate the ComponentMessageSourceImpl and enhance it
> with your requirements.
>
> Best regards,
> Gerold
>
>
> 2012/4/10 Henrik von Schlanbusch <hen...@enovate.no>
>
>> Henrik von Schlanbusch <henrik <at> enovate.no> writes:
>>
>>>
>>> Hi
>>>
>>> We have made a locale service that extracts messages from the
>>> database based on keys. We would like to use the service
>>> from the tml files, and preferably to replace the
>>> default tapestry ${message:SOME_KEY} to use our
>>> implementation. Is this possible to do in T5 so we can
>>> still write ${message:SOME_KEY} but the keys are
>>> extracted using our service?
>>>
>>
>> I found no good solution for this, so I implemented a component
>> that did the trick. It would be cool, though, to be able to
>> replace the default ${SOME_KEY} with own implementation.
>>
>> Still, Tapestry 5 is totally awesome :-)
>>
>> Henrik
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
>> For additional commands, e-mail: users-h...@tapestry.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
