its very hard to figure out problems like this without having running
code. you can either create a quickstart with a failing testcase, or
even better make a pull request on github that will add the failing
testcase directly into the codebase.
thanks,
-igor
On Mon, Nov 21, 2011 at 12:34 PM, Jablo
Igor>but you can create a testcase, reproducing the bare bits of code in a
testcase just like you did in the email below. the advantage would be
that i would have something i can play with which makes it much easier
to find the problem.
I will work on a quick start tonight, when I'm not at work.
On Fri, Nov 18, 2011 at 9:32 AM, Jablow, Eric R wrote:
> Dear Igor,
>
> (me)>> I get a call with expression being "child", and target being the local
> test object. Were expression "parent.child", this would succeed, as it would
> call getParent().getChild(). However, I'm not sure whether this
Dear Igor,
(me)>> I get a call with expression being "child", and target being the local
test object. Were expression "parent.child", this would succeed, as it would
call getParent().getChild(). However, I'm not sure whether this is my bug or
the wicket-validation-bean library's.
(Igor)>this
inline,
On Thu, Nov 17, 2011 at 4:05 PM, Jablow, Eric R wrote:
> I have some model classes with JSR 303 validation annotations, and I have
> some FormComponentPanels for each. Some of these will be nested. To test that
> the Wicket validation is correct, I'm creating a ValidationForm, which
>
I have some model classes with JSR 303 validation annotations, and I have some
FormComponentPanels for each. Some of these will be nested. To test that the
Wicket validation is correct, I'm creating a ValidationForm, which contains one
of my panels, which contains another of my panels, and I am
