Chris Nokleberg wrote:
Right. The idea was to perhaps find a better way to accomplish the same thing. Once a good way has been found, then we can discuss various optimizations of it.Oops: "this is to me an obvious case of premature optimization". But optimization is a maybe not the best word for omitting a feature completely :-)
But that can break too, if you're using defaulted values. Let's say you have a property that can be set called "foo" and that default is 5. If you're happy with that then you do nothing in the XML descriptor, and thus expect 5 to be the value. Then a user could override it using a parameter.I'd like to see properties on results as well as action mappings, which would be applied to the chained action. There are some interesting questions regarding the ordering of all the parameter setting, though. I'd prefer that the action properties overwrite any form parameters. If you're using the properties to parameterize the execution of the action from your config file, you don't want the user to be able to mess with things just by guessing the right property name.
Another reason why doing action configuration this way is a bad idea in the first place I guess.
/Rickard
--
Rickard Öberg
[EMAIL PROTECTED]
Senselogic
Got blog? I do. http://dreambean.com
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
