Andrei,
I understand about org.apache.avalon.framework.configuration.Configuration,
but that is not what is exposed to matchers and mailets. If that is what
people decide should be exposed, then we don't even have to add methods;
just expose the underlying configuration object. All that is currently
exposed is a simple name=value approach, similar to that used elsewhere in
Java, e.g., Servlets. I was not proposing changing that scheme.
> you don't know if the element is intended for the matcher
> or mailet configuration.
> No this is not so. Child element is always specified as a method
parameter.
My proposal keeps parameters for matchers and parameters for mailets
separate, so that there isn't a chance of namespace collision. Remember
that matchers and mailets should be capable of arbitrary mixing. As I see
it, your scheme flattens and merges the name spaces.
--- Noel
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
