When you inject a service, Tapestry works primarily by the type (whether its
the type of a field in a component, or the type of a parameter to service
builder method or a constructor).
When resolving, based on type, Tapestry will search all the services defined
by any and all modules, looking for
On Thu, May 31, 2007, SergeEby wrote:
> You can provide your own implementation by contributing to aliasOverrides:
>
> http://tapestry.apache.org/tapestry5/tapestry-core/guide/alias.html
Thank you for your reply. I took a look at that page, but I do
not quite understand it. It seems like I lack
Hi,
You can provide your own implementation by contributing to aliasOverrides:
http://tapestry.apache.org/tapestry5/tapestry-core/guide/alias.html
/Serge
Martin Dietze wrote:
>
> Hi,
>
> I need to use a particular localization backend for my
> project. As I understand, T5 provides its own
Hi,
I need to use a particular localization backend for my
project. As I understand, T5 provides its own code for
retrieving messages based on the .properties files, and if
I understand Howard's posting from Mar 4 right, simply
plugging in my own ComponentMessageSource implementation
is not yet s
