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: [email protected] For additional commands, e-mail: [email protected]
