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. Antoine On Tue, Mar 2, 2010 at 12:33 PM, Sergey Olefir <solf.li...@gmail.com> wrote: > > > Thing is, I already toyed with WebRequestCodingStrategy -- specifically I > changed how resources are encoded by replacing URL path with URL parameter. > And I broke CSS/relative references in the process as I found out much later > :) (as you found out already in your another post ;)) > > Although if I do something less drastic -- such as simply encoding the > section with FQN -- I might break less stuff... Ah well, as you pointed out > (and special thanks for that :)), 1.4.7 hopefully will be out soon with the > some fix for the issue, maybe I can just wait it out. > > > bgooren wrote: >> >> So I had a quick look at the source code of WebRequestCodingStrategy, and >> I think it should be possible to create a solution for your problem quite >> easily: >> > > -- > View this message in context: > http://old.nabble.com/How-to-encrypt-obfuscate-resource-reference--tp27744679p27754796.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > -- take your photos everywhere you go - https://www.memolio.com follow us on Twitter - http://twitter.com/Memolio --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
