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

Reply via email to