Next Major was ok.
Everything we put in trunk before we'll branch will be in Next Major
*unless* we decide something specific about specifc issues/code.
Otherwise maybe we misunderstood each other in the roadmap planning...
Stefano
Bernd Fondermann (JIRA) wrote:
[ http://issues.apache.org/jira/browse/JAMES-635?page=all ]
Bernd Fondermann updated JAMES-635:
-----------------------------------
Fix Version/s: Trunk
Make information about configured Processors, Mailets and Matchers available at
runtime
---------------------------------------------------------------------------------------
Key: JAMES-635
URL: http://issues.apache.org/jira/browse/JAMES-635
Project: James
Issue Type: New Feature
Components: Remote Manager, SpoolManager & Processors
Affects Versions: Next Major
Reporter: Bernd Fondermann
Assigned To: Bernd Fondermann
Fix For: Trunk
Attachments: screenshot_jconsole.png
Add functionality to RemoteManager and JMX interface to show all Processors and
related Mailets and Matchers.
(JAMES-123 is a similar issue, but more targeted towards reading the classpath,
so I am opening a new and fresh JIRA.)
In the RM, the Processor names can be listed, and furthermore all Mailets and
Matchers for one Processor.
In JMX, each Processor, Mailet and Matcher has its own MBean and they are
naturally being grouped by the JMX client in a tree representing the
parent/child relationships between Processor and Mailets/Matchers.
Names and configuration parameters are shown in the basic version.
Additionally, I would like to add live statistics about how many mails were
processed and to support JMX notifications for live problem analysis without
restarting the server for adding logger mailets or otherwisely interrupting the
running server.
Currently, I am not planning to make it possible to alter configuration
parameters at runtime or to re-wire the processing chain. This is postponed for
future decision.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
