Please create a jira issue for it.
We are planning to redo the testing part of wicket to make it consistent and
up-to-date for 1.4/2.0.
Frank
On Thu, Mar 6, 2008 at 2:29 PM, Wojciech Biela [EMAIL PROTECTED] wrote:
Hey
It looks like a bug but it's so obvious I suspect it's a feature not a
Hey
It looks like a bug but it's so obvious I suspect it's a feature not a
bug, a feature I yet have learn to appreciate.
When I assert a value on a component and the path is invalid (either
the component is not there or I misspelled the path) the assertion
fails. This is fine.
When I try to
