RE: [Springframework-developer] java.util.Map fields and commons validator

[Baum, K. <Kar...@Ta...>]

My issue is more with compatibility between commons validator and
spring.  Currently today, to denote a mapped property in spring we use
the '[' character.  However when this is sent to commons validator, it
will not be able to find this property in the bean as it will be =
looking
for an indexed property as opposed to a mapped property.

-----Original Message-----
From: spr...@li...
[mailto:spr...@li...] On =
Behalf
Of Colin Sampaleanu
Sent: Wednesday, April 14, 2004 7:57 AM
To: spr...@li...
Subject: Re: [Springframework-developer] java.util.Map fields and
commons validator

The existing spring approach is also similar to OGNL. In OGNL, '(' is=20
used for an actual method call, since you can also call methods, not=20
just navigate graphs.

I'm a bit of mixed feelings about adding '(' support in the =
BeanWrapper.

It would make the validation usage a bit more similar to=20
commons-validator/struts, but would muddy the water for general=20
expression syntax.

Karl, your issue with the setup right now is that people can't take=20
their existing definitions exactly as-is?


j=FCrgen h=F6ller [werk3AT] wrote:

>Karl,
>=20
>Agreed, it makes sense to be consistent with Commons BeanUtils /
Commons Validator / Struts here, while still supporting the current
syntax. Our current syntax is somewhat analogous to JSTL EL, but I =
don't
mind supporting further syntactic options, as long as they don't
introduce parsing problems.
>=20
>This should be pretty trivial to add, so I'll look into it this
weekend.
>=20
>Juergen
>=20
>
>________________________________
>
>Von: spr...@li... im Auftrag
von Baum, Karl
>Gesendet: Mi 14.04.2004 04:19
>An: spr...@li...
>Betreff: [Springframework-developer] java.util.Map fields and commons
validator
>
>
>
>I have encountered an issue in regards to validating beans backed by a
>Map object while using the spring commons validator component.  My =
form
>is made to work with key value pairsbacked as a map.  It has a field:
>
>     /**
>      * @return
>      */
>     public Map getValue() {
>         return valueMap;
>     }
>
>     /**
>      * @param map
>      */
>     public void setValue(Map map) {
>         valueMap =3D map;
>     }
>
>The problem isn't specific to the validator adapter.  The problem has
to
>do with the way Spring symbolizes a mapped property in the
>BeanwrapperImpl class.  Spring uses a '[' where as commons validator
and
>struts use '('.  Another words a mapped property of firstName would
look
>like this in Spring:
>
> value[firstName]
>
>and this in commons validator:
>
> value(firstName)
>
>Commons validator uses '[' for indexed properties.  Spring uses '[' =
for
>both indexed and Mapped properties.  I think the best place to fix =
this
>problem is on the Spring side in the BeanWrapperImpl.  We might as =
well
>be consistent with struts and commons validator in regards to our
>indexed and mapped property sytax.  Perhaps we can support both
>syntaxes.=20
>
>Any thoughts?
>
>Karl
> =20
>




-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=3D1470&alloc_id=3D3638&op=3Dcl=
ick
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer