Just a thought...
I've been using Wicket 10 snapshot builds in production for over a year now
with latest Spring and Jakarta libs without any major issues, so if that is
an option for you, go ahead. You can mitigate risks by creating release
from a known git rev yourself if your release process
Easiest way to do it is to create a custom resource loader like this:
public class DatabaseResourceLoader implements IStringResourceLoader {
(...)
@Override
public String loadStringResource(Class clazz, String key, Locale
locale, String style, String variation) {
return
