> -----Original Message----- > From: Rickard Öberg [mailto:[EMAIL PROTECTED] > > Why are "params" declared explicitly? What's wrong with finding them > implicitly, as is done in WebWork? Sounds like a refactoring disaster > waiting to happen. Any configuration that is mostly just > duplication of > code is a bad idea IMHO.
There are 2 types of parameterization, and you're free to use either or both. The params in the configuration are static params which are intended to parameterize a reusable Action for one or more aliases. For instance, if you had an email action you might parameterize it with the server address, etc. > > Also, it is in general VITAL that we try to keep the configuration > required for each action/command down to a minimum. Consider > the above > when you have 50-100 commands/actions. That's a lot of stuff to keep > track of. You don't HAVE to put params, etc. into the config, but you can if you need to. > Why not XMLConfigurationProvider? I mean, that's what it is. Sure, that sounds ok. > > > SimpleConfiguration -> SimpleConfigurationProvider > > Why not TestConfigurationProvider? I mean, that's what it is. > Sure. ------------------------------------------------------- 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
