Blower, Andy wrote:
Not sure how generally useful that would be, but it would solve the problem in
an easy way.
Thinking some more about this, would it not be easier to simply pass the
messages from the page/component event handler method into the service method
that's called to send the emai
method
> that's called to send the email?
>
>> -Original Message-
>> From: Howard Lewis Ship [mailto:hls...@gmail.com]
>> Sent: 06 February 2009 21:26
>> To: Tapestry users
>> Subject: Re: Localization in Services
>>
>> Which Messages resour
Original Message-
> From: Howard Lewis Ship [mailto:hls...@gmail.com]
> Sent: 06 February 2009 21:26
> To: Tapestry users
> Subject: Re: Localization in Services
>
> Which Messages resource would it inject?
>
> I suppose we could add the application's Messages obj
ike you can with Logger. I take it that this is
> not possible to provide in T5 because of lifecycle/reloading issues then
> Howard?
>
>> -Original Message-
>> From: Howard Lewis Ship [mailto:hls...@gmail.com]
>> Sent: 06 February 2009 17:03
>> To: Ta
s Ship [mailto:hls...@gmail.com]
> Sent: 06 February 2009 17:03
> To: Tapestry users
> Subject: Re: Localization in Services
>
> I would go a different route.
>
> Using the ComponentSource service, you can get any page in the
> application as a Component instance.
I would go a different route.
Using the ComponentSource service, you can get any page in the
application as a Component instance.
>From that you can get the ComponentResources and from that, the Messages
>object.
Just be aware of the lifecycle: once you boost a Messages instance out
of the comp
Thanks for the tip Roberto, but I didn't succeed into adding the
app.properties (or just i can't get the key, i don't know)
And it feels strange to use the ValidationMessage for a standart message
Nick
Tapestry Infodea wrote:
I've forgetten a piece of code, you must contribute the
ValidationMe
I've forgetten a piece of code, you must contribute the
ValidationMessagesSource in your AppModule:
public void
contributeValidationMessagesSource(OrderedConfiguration
configuration) {
configuration.add("myprop", "it/infodea/app/internal/myprop");
}
and define myprop.properties in it
You can use the ValidationMessagesSource and ThreadLocale services:
ValidationMessagesSource validationMessagesSource;
ThreadLocale threadLocale;
Messages messages =
validationMessagesSource.getValidationMessages(threadLocale.getLocale());
Roberto.
Nicolas Charles ha scritto:
Hello there,
Hello there,
I'm currently struggling with a proper way to use localization in a
service. My need is fairly simple : i'm using t5-restful-webservices
from Bill Holloway (by the way great job Bill) to offer REST services.
One of my service sends an email. The email is localized. Using the
Asset
10 matches
Mail list logo
