why not simply have exception provide resource key for messages
instead of messages themselves, that way you can do
onclick() {
try { dosomething(); } catch (BusinessException e) {
error(getString(e.getMessageKey())); }
}
ie push the actual localization into the ui.
-igor
On Feb 3, 2008 12:15 PM, oliverw <[EMAIL PROTECTED]> wrote:
>
> In my Wicket frontend I'm making heavy use of Wicket's excellent localization
> feature (wicket:message tag and attribute). Now I would like to unify my
> localization efforts, thus using the wicket localizer at my service backend
> for localizing messages of exceptions reaching the frontend.
>
> Being new to both wicket and java I thought it might be a good idea to fire
> a question about the feasibility of passing a Wicket Localizer down to my
> services before implementing it. I don't know but it sounds just a bit odd
> to introduce a dependency to a UI framework at the service level and maybe
> there's a standard (java) way of doing exception localization which I have
> overlooked - although I couldn't find one during my investigations.
> --
> View this message in context:
> http://www.nabble.com/Localization-Question-tp15257675p15257675.html
> Sent from the Wicket - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
