Hi Martijn,
> MessageFormat is pretty much canonical
indeed, it's like java.util.Date: It has been there forever, everyone
uses it, but it has its quirks :P.
> Having one message format across both backend and frontend is beneficial
Is it beneficial because you're using the same resource bundles in
backend and frontend?
Don't you ever use Wicket's property resolving ${foo} in your messages?
Have fun
Sven
On 09/28/2014 08:48 PM, Martijn Dashorst wrote:
On Wed, Sep 24, 2014 at 12:44 AM, Sven Meier <[email protected]> wrote:
Additionally to the var-args vs array decision, I don't like that we are
using MessageFormat for this: it has a foreign syntax {0}, it's index-based
and it doesn't work with Wicket converters.
The one problem I see is that MessageFormat is pretty much canonical.
At €work we are juggling how to do I18N in our rest backend and our
Wicket frontend... We don't have Wicket available in the backend so we
are **forced** (ahum) to use resource bundles and message format at
that point. Having one message format across both backend and frontend
is beneficial.
Martijn
