On Thu, Jan 02, 2003 at 09:23:19PM +0100, Rickard Öberg wrote: > Chris Nokleberg wrote: > > 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. > > 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 don't understand this logic. A property default is a default for form parameters, obviously it can change. If you want to fix the value for a particular mapping, you add it to actions.xml. The argument that it will hurt performance is really misleading IMHO. You're assuming a certain implementation. For one thing, since the parameters and values and destination classes are known ahead of time, you can pre-convert all of the values. etc., etc. -Chris ------------------------------------------------------- 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
