[ http://issues.apache.org/jira/browse/JAMES-469?page=comments#action_12373648 ]
Noel J. Bergman commented on JAMES-469: --------------------------------------- Excellent, thanks. If you go back and look at last year's discussions regarding pluggable handlers, you'll find the following in the e-mail archives: "The proposal I put forth wasn't just fast-fail, but pluggable in-protocol handler packages. In fact, as I envision it, the "base" package would include the default onMessage handler that knows how to post a message into the spool. That makes even that mechanism pluggable." So this is a good change. As for Avalon interfaces, I'd expect to move away from all such things when we "POJO-ify" JAMES. > Make SMTP message queuing configurable (as an Handler) > ------------------------------------------------------ > > Key: JAMES-469 > URL: http://issues.apache.org/jira/browse/JAMES-469 > Project: James > Type: Improvement > Components: SMTPServer > Versions: 2.3.0a1 > Reporter: Stefano Bagnara > Assignee: Stefano Bagnara > Priority: Minor > Fix For: 2.3.0a2 > > The current message receiving code could be moved to an Handler to improve > configurability. > This need a configuration change in the default smtphandlerchain. I added a > blocking configuration error message if there is no messagehandler configured. > To do that we need to improve the lifecycle of the handlers: configurable and > serviceable handlers must be supported. > We could even move the chain configuration to an avalon component level > (removing avalon/lifecycle specific code from the handler). -- 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]
