Create a unit test case that scans your application for resources and
checks if the class is set. If not, fail. If set, check if it is
unique, if not fail.

Martijn

On Tue, Mar 2, 2010 at 12:40 PM, Sergey Olefir <solf.li...@gmail.com> wrote:
>
>
> 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: 
> http://old.nabble.com/How-to-encrypt-obfuscate-resource-reference--tp27744679p27754862.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
>
>



-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.4 increases type safety for web applications
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.4

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Reply via email to