The combination of wicket:message and custom IStringResourceLoader is really
cool for building internationalized applications. We currently use a
combination of static strings from property files and dynamic strings stored in
a database table loaded via an IStringResourceLoader.
To edit a
Check org.apache.wicket.markup.resolver.WicketMessageResolver
This is the default handler for wicket:message and it is registered in
org.apache.wicket.Application.internalInit()
See whether you can extend it.
The idea is to generate a href=... super.onComponentTagBody() /a
On Wed, 2010-07-14 at
or rather create a component and use that instead of wicket:message
-igor
On Wed, Jul 14, 2010 at 5:21 AM, Martin Grigorov mcgreg...@e-card.bg wrote:
Check org.apache.wicket.markup.resolver.WicketMessageResolver
This is the default handler for wicket:message and it is registered in
Hmm, yes, but then I'd have to add lots of tiny components to my pages. One of
the main points of wicket:message is to avoid just that, isn't it?
Regards,
Harald
Von: Igor Vaynberg [igor.vaynb...@gmail.com]
or rather create a component and use that
