> Well, you'd be "set"-ing it into one of x scopes :-) Yeah, yeah, I guess you're right. I just think it may have the potential to be a confusing tag if not documented properly. Someone could mistake it like this:
<ww:bean name="webwork.util.Counter" name="id"> <ww:set name="first" value="1"/> <ww:set name="last" value="5"/> </ww:bean> I know in ww 1.x we use param, but someone could easily mistake it for a set, which is why I suggested scope. Set works for me, but it has to be documented well. Make sense? rick ------------------------------------------------------- This SF.net email is sponsored by:Crypto Challenge is now open! Get cracking and register here for some mind boggling fun and the chance of winning an Apple iPod: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
