You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Igor Vaynberg <ig...@gmail.com> on 2009/04/07 19:04:35 UTC
Re: Is localizing parts of the service layer (which is using Spring
2.5) a good idea?
both wicket and spring allow you to customize how text bundles are
loaded. you can create a spring bundle loader that uses your
webapplication.properties file or a wicket bundle loader that uses
your spring bundle. either way you can then have business tier and web
share certain text bundles for localization. once that is done, it
hardly matters which layer performs localization since they are backed
by the same dictionary.
-igor
On Tue, Apr 7, 2009 at 3:01 AM, Kent Larsson <ke...@gmail.com> wrote:
> Hi,
>
> This is more of a general design question and I would really
> appreciate some input. Do you localize the service layer as well as
> the Wicket presentation layer?
>
> I have a specific use case. When a user register a new account the
> service layer sends an e-mail message with an activation link. This
> message should be written in a language which the users understands
> and must thus be localized. I see two options:
>
> 1: Localize it using Spring only and don't involve Wicket. That way it
> will work in case of a user registering an account through a web
> service (bypassing the Wicket presentation layer).
>
> 2: Use localization as you normally would from Wicket and send the
> message string from the presentation layer to the relevant service
> layer method (where it is used in the e-mail).
>
> Currently no user is supposed to register through a web service
> invocation. It might change though, but not for quite a while.
>
> How would you solve this problem?
>
> Best regards, Kent
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Is localizing parts of the service layer (which is using Spring
2.5) a good idea?
Posted by Kent Larsson <ke...@gmail.com>.
Great answer as you always seem to provide Igor! Thank you!
/ Kent
On Tue, Apr 7, 2009 at 7:04 PM, Igor Vaynberg <ig...@gmail.com> wrote:
> both wicket and spring allow you to customize how text bundles are
> loaded. you can create a spring bundle loader that uses your
> webapplication.properties file or a wicket bundle loader that uses
> your spring bundle. either way you can then have business tier and web
> share certain text bundles for localization. once that is done, it
> hardly matters which layer performs localization since they are backed
> by the same dictionary.
>
> -igor
>
> On Tue, Apr 7, 2009 at 3:01 AM, Kent Larsson <ke...@gmail.com> wrote:
>> Hi,
>>
>> This is more of a general design question and I would really
>> appreciate some input. Do you localize the service layer as well as
>> the Wicket presentation layer?
>>
>> I have a specific use case. When a user register a new account the
>> service layer sends an e-mail message with an activation link. This
>> message should be written in a language which the users understands
>> and must thus be localized. I see two options:
>>
>> 1: Localize it using Spring only and don't involve Wicket. That way it
>> will work in case of a user registering an account through a web
>> service (bypassing the Wicket presentation layer).
>>
>> 2: Use localization as you normally would from Wicket and send the
>> message string from the presentation layer to the relevant service
>> layer method (where it is used in the e-mail).
>>
>> Currently no user is supposed to register through a web service
>> invocation. It might change though, but not for quite a while.
>>
>> How would you solve this problem?
>>
>> Best regards, Kent
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org