On 8/30/06, Stefano Bagnara <[EMAIL PROTECTED]> wrote:
Bernd Fondermann wrote:
> For some time now I've been playing around with the idea of displaying
> the Processor, Matcher and Mailet hierarchy through JMX. (Good to know
> there is already a JIRA for it.) This could be used to manage mailet
> settings online. Much later, it could be used to manage the hierarchy
> itself.
>
> So I think this could be useful.
>
> It would probably mean to expose the hierarchy internally to the
> management components.
Unfortunately that changes could not be made persistent in an easy way.
if we say that this is causing too much user errors, we could fall
back to read-only access.
I think that the first useful feature that we can get from being bale to
navigate the matcher/mailet tree is to administer them.
As an example the bayesian tasks that we added to the remotemanager and
that have duplicate configuration could be changed to interact directly
with the mailet. We could have each mailet to expose its own management
tasks.
do we have to extend the mailet API for that? for example by adding an
MailetMBean interface?
Bernd
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
