I was earlier returning a *** kind of String when the Spring MessageSource
failed to resolve the key (so that missing error messages would be
obvious). Obviously that was the wrong thing to do. The trick is to return
null so that Wicket continue trying to resolve the message in the sequence
you
Hi,
I'm migrating an existing (Spring MVC) JSP application to Wicket and this
application already has i18n with just one largish properties file, named as
per Spring tradition messages.properties.
I'm using Wicket 1.2.4. I was able to easily delegate looking up of
messages to Spring's
i believe the search order is to first try the id.key and then to try key,
so your messages should still resolve properly. can you break in localizer
and see what its doing?
-igor
On 2/3/07, Peter Thomas [EMAIL PROTECTED] wrote:
Hi,
I'm migrating an existing (Spring MVC) JSP application to
