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

[Hunter K. <re...@ei...>]

I have to say that I personally prefer [] syntax for both indexed and map=
ped
properties, it's a more natural fit with scripting languages, and to me i=
t
just makes more sense - it's an indexing operation, not a method call!

My point is that it'd be great to support other syntaxes, but please
keep the [ syntax.

H

On Wednesday 14 April 2004 07:44, j=FCrgen h=F6ller [werk3AT] wrote:
> Karl,
>
> Agreed, it makes sense to be consistent with Commons BeanUtils / Common=
s
> 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.
>
> This should be pretty trivial to add, so I'll look into it this weekend.
>
> Juergen
>
>
> ________________________________
>
> Von: spr...@li... im Auftrag v=
on
> 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 t=
o
> do with the way Spring symbolizes a mapped property in the
> BeanwrapperImpl class.  Spring uses a '[' where as commons validator an=
d
> struts use '('.  Another words a mapped property of firstName would loo=
k
> 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.
>
> Any thoughts?
>
> Karl
>
>
> -------------------------------------------------------
> 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=3Dc=
lick
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>
>
>
>
> -------------------------------------------------------
> 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=1470&alloc_id638&op=3DClick
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer