Looks like it's fixed in beta-34
On Tuesday, August 11, 2015, Thiago H de Paula Figueiredo <
thiag...@gmail.com> wrote:
> On Tue, 11 Aug 2015 19:04:22 -0300, Barry Books wrote:
>
> Is there a later public beta? I did try beta-6 and it works fine so the
>> problem is newer than that.
>>
>
> There
You’re right. And it happens with programmatic validation, too. Try “Acme” into
First Name of these examples which currently running on beta-26:
http://jumpstart.doublenegative.com.au/jumpstart7/examples/input/edit1/1
http://jumpstart.doublenegative.com.au/jumpstart7/examples/inp
On Tue, 11 Aug 2015 19:04:22 -0300, Barry Books wrote:
Is there a later public beta? I did try beta-6 and it works fine so the
problem is newer than that.
There are later sort-of-public betas if you add
https://repository.apache.org/content/repositories/staging/ as a Maven
repository:
h
seems OK in beta-22 also
On Tuesday, August 11, 2015, Barry Books wrote:
> Is there a later public beta? I did try beta-6 and it works fine so the
> problem is newer than that.
>
> I did also figure out I can reproduce the problem with a form and two
> property editors.
>
> On Tuesday, August 11
Is there a later public beta? I did try beta-6 and it works fine so the
problem is newer than that.
I did also figure out I can reproduce the problem with a form and two
property editors.
On Tuesday, August 11, 2015, Thiago H de Paula Figueiredo <
thiag...@gmail.com> wrote:
> On Tue, 11 Aug 2015
On Tue, 11 Aug 2015 17:36:57 -0300, Barry Books wrote:
I stumbled across a problem with server side validation and
BeanEditForm. I
have some server side validation that takes a case number and validates
it's in the database. It's done with a JSR 303 validator. The problem is
when the field is
