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.
Bernd
On 8/29/06, Norman Maurer (JIRA) <[email protected]> wrote:
[ http://issues.apache.org/jira/browse/JAMES-123?page=all ]
Norman Maurer updated JAMES-123:
--------------------------------
Bugzilla Id: (was: 22610)
Assignee: (was: Norman Maurer)
I will not do this. Im also not sure if we really need this.
> List matchers and mailets
> -------------------------
>
> Key: JAMES-123
> URL: http://issues.apache.org/jira/browse/JAMES-123
> Project: James
> Issue Type: New Feature
> Components: Remote Manager
> Affects Versions: 2.1
> Environment: Operating System: Other
> Platform: Other
> Reporter: Serge Knystautas
> Priority: Minor
> Fix For: 3.0
>
>
> Add to remote manager the ability to list what matchers and mailets are
> currently available in the classpath. This would have to be through
reflection
> somehow, although the list of packages to scan would be defined in the conf
file
> (and should be listed as part of these commands).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
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]
