On Mon, 24 Jan 2005 06:13:23 -0700, Larry Meadors <[EMAIL PROTECTED]> wrote: > OK, I think i understand what you are trying to do. You could override > the constructor of your action to read in a properties file. If you > have multiple actions, you could make it a base class that uses some > common naming convention, that may simplify things.
You could also implement this as a filter, which will give you more options then an action for this kind of thing. Espeically in terms of adding this check to a lot of different URLS. > > > On Mon, 24 Jan 2005 08:02:04 +0000 (UTC), <[EMAIL PROTECTED]> wrote: > > On 2005-01-24, Larry Meadors <[EMAIL PROTECTED]> wrote: > > > > > Maybe we are approaching this from the wrong direction. what is > > > the problem you are trying to solve? > > > > Perhaps I am. I have an action which retrieves a couple of values > > from a database. If the retreival fails, it return some reasonable > > default values instead. It is these defaults which I want to be > > user configurable, that is, configurable from some initialization > > file. > > > > The introspection/set-parameter feature, found in PlugIns, would > > solve my problem, but it isn't available for actions, only > > actionmappings. > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
