Hi,
I observed a weird behavior with select components after upgrading to Stripes
1.5. It can easily be reproduced.
I put 2 select components with similar attributes, and only the first one is rendered correctly; the other is missing
attributes. Ex:
etting us dump JSF and
> switching to Stripes in the first place. The amount of swearing
> in the developers' area has since reduced dramatically ;-)
>
> Cheers,
> Freddy
>
> -
> - Why wait?
> -
> - On Apr 15, 2008, at 12:21 PM, Mathieu Avoine <[EMAIL PROTECTED
th
> three-digit groupings...
>
> -t
>
> On Apr 15, 2008, at 11:13 AM, Mathieu Avoine wrote:
>
>> Hi all,
>>
>> I noticed that if I enter the value 56xlk9293 in a field bound to
>> an Integer property, the value gets converted to 56.
>> The
Hi all,
I noticed that if I enter the value 56xlk9293 in a field bound to an Integer
property, the value gets converted to 56.
The behavior seems incorrect to me, as the string enter contains a bunch of
characters that are not numbers. Also, if I
enter "1,56", it is converted to 156! Needless t
Hi,
I have a problem with a wizard form where some value is not set at some point.
I checked the logs and I found this:
2008-04-10 10:24:51 DEBUG mavoine: Log.trace: Running binding for property with
name: keys.selectedIdsString
2008-04-10 10:24:51 DEBUG mavoine: Log.debug: Converting 1 value(s
, at least, 1 is not equal to 0 ;-)
Any idea what I could be doing wrong?
Thanks,
Math
Mathieu Avoine wrote:
> Hi,
>
> I want to use annotation driven validation to validate that a property
> of type List contains at least 1 item (i.e. mylist.size() > 0).
>
> I tried using
Hi,
I want to use annotation driven validation to validate that a property
of type List contains at least 1 item (i.e. mylist.size() > 0).
I tried using required=true, because I would have expected the behavior
for a List object to check for the size, but it looks like it only
validates if the
