see IResourceSettings#setThrowExceptionOnMissingResource(boolean)
-igor
On Wed, Mar 11, 2009 at 8:57 AM, Swanthe Lindgren <
swanthe.lindg...@megasol.se> wrote:
> Is there a similar way to ensure that all wicket:message key resources
> exist?
>
> //Swanthe
>
>
> Igor Vaynberg wrote:
>
>> if you w
Is there a similar way to ensure that all wicket:message key resources
exist?
//Swanthe
Igor Vaynberg wrote:
if you want the removal of wicket:id to fail turn on component use
check in debug settings.
-igor
On Tue, Mar 10, 2009 at 3:12 AM, Swanthe Lindgren
wrote:
Hi all
I have begun uni
if you want the removal of wicket:id to fail turn on component use
check in debug settings.
-igor
On Tue, Mar 10, 2009 at 3:12 AM, Swanthe Lindgren
wrote:
> Hi all
> I have begun unit testing my wicket pages and one of the most basic tests I
> want to do is to make sure each and every page can r
Yes - it simply makes sure THAT page rendered. Removing the wicket:id doesn't
make the page fail to render. However, try the inverse of that - remove the
component from the java and it will fail.
Jeremy Thomerson
http://www.wickettraining.com
-- sent from a wireless device
-Original Messa
