[JAMES-3804] Improve error handling when mailetContainer misses a processor

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.7.0
• Fix Version/s: 3.8.0
• Component/s: Mailet Contributions
• Assignee: Unassigned
• Reporter: Benoit Tellier
• Created: 16/Aug/22 03:01
• Updated: 23/Aug/22 01:19
• Resolved: 23/Aug/22 01:19

Description

Today, if I specify a mailet pointing to a processor that do not exist, James will start, and the failure will be managed at runtime: upon processing, each mail needed to be processed by the unspecified processor will instead go to the error processor.

Recovering data from such a failure is quite a journey in itself.

Example of such configuration:

<mailet matcher="All" class="ToProcessor">
    <processor>notFound</processor>
</mailet>

Instead of handling such failures at runtime, we could instead abort James startup.

Given we add a new method on the mailet interface, for a mailet to give the list of processor it needs, we can trivially implement such a check in the mailet container.

Definition of dome: Have an integration test with configuration specified above, james should fail to start.

Issue Links

• links to: GitHub Pull Request #1128