Thanks for heads up.

I guess it's back to hacking WebRequestCodingStrategy for me, the flag is
better than nothing, but I'm not eager in having application crash in
production because someone forgot to map something and somehow it slipped
past testing.

Antoine van Wel wrote:
> A flag has been introduced that when set will throw an error when an
> fqn would be used. It will be in 1.4.7, which is currently in the
> voting phase, so it will be available within a week.
> But this would mean you'd have to alias all the classes anyway.

View this message in context:
Sent from the Wicket - User mailing list archive at

To unsubscribe, e-mail:
For additional commands, e-mail:

Reply via email to