|
From: JP P. <jp....@ti...> - 2003-05-30 10:05:25
|
Rod, I'm inclined too to favor this. But I see another improvement without having now the right solution about the map. In UrlHandlerMapping the data is in fact a bean reference and this is not already checked. In methodNameResolver in contrast, it's a simple text (method name). Perhaps will we have an unique value/ref in the map entry body instead of simple text? <property name=3D"mappings"> <map> <entry key=3D"/welcome.html"><ref = bean=3D"pagedListController"/></entry> <entry key=3D"/detail.html"><ref = bean=3D"pagedListController"/></entry> </map> </property> <property name=3D"mappings"> <map> <entry key=3D"/welcome.html"><value>showMain</value></entry> <entry key=3D"/detail.html"><value>showDetail</value></entry> </map> </property> Regards, Jean-Pierre > -----Message d'origine----- > De : rod...@in... [mailto:rod...@in...]=20 > Envoy=E9 : vendredi 30 mai 2003 11:24 > =C0 : JP Pawlak > Cc : 'Rod Johnson'; spr...@li... > Objet : Re: RE : [Springframework-developer] DTD >=20 >=20 > JP, >=20 > I agree, formalizing map support would be an improvement. I'm=20 > not sure we can do it for 0.8, though. Presently it's handled=20 > by a PropertyEditor. >=20 > I wonder if it means we should introduce additional container=20 > elements <list> and <map> into our DTD? e.g.: >=20 > <property name=3D"simple"><value>val</value></property> > <property name=3D"mappings"> > <map> > <entry key=3D"/welcome.html">pagedListController</entry> > <entry key=3D"/detail.html">pagedListController</entry> > </map> > </property> >=20 > <property name=3D"coll"> > <collection> > <value>val</value> > <ref bean=3D"foo"/> > </collection> > </property> >=20 > It's getting still more verbose, but it would be easier to=20 > parse and is more elegant. (Don't need to guess whether a=20 > value/ref is part of a collection.) >=20 > I'm inclined to favour this. I could probably implement it by=20 > early next week (including maps). >=20 > Regards, > Rod >=20 |