That was along the lines of what I was thinking.
The folks over at the James project have written so many useful matchers, I
thought it would be really useful to be able to use what has already been
written. For instance, one of the latest ones I saw was an anti-virus scanning
Matcher using
Look, it sounds like you really like JAMES and want to use JAMES, so go use
JAMES
Tsk Tsk Andy.
Just because someone says he likes some design features of a competing piece of
software is no reason to be so dismissive.
There are things I think I would like about using James, like its
I'm curious about people's thoughts about the James Mailet API as a design for
e-mail processing after it's been accepted by the SMTP server. (The api is
described at http://james.apache.org/mailet_api_2_1.html)
Since I've already received Andy's views on this, I'd like to hear from others
Andy,
Thank you for your reply.
Jack
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3870659#3870659
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3870659
---
SF email
Andy,
Thanks for that reply. I am curious to learn more of your thoughts about the
Mailet API.
In considering James, I liked the idea of being able to chain standard and
custom matchers to handle mail processing. It seems like a very flexible,
almost aspect-oriented, approach to handling
Thanks for the reply.
The JMSMailListenerMBean interface is definitely along the lines of what I'm
looking for in terms of decoupling the socket-level server stuff from the
business code.
I'll take a look at the code in more detail and try out M2.
As for the MailListener interface, is there
Is there a reason why JBoss Mail shouldn't adopt the Apache James Mailet /
Matcher API? It seems well documented and is a stable, well thought out API
for e-mail workflow processing.
Honestly, I've looked at (am still looking at) James as an e-mail server
solution for an upcoming project. I
I was thrilled when I came across the Apache James e-mail server a couple years
ago, but after a bit of investigation, I decided not to embrace it. I really
liked the Matcher / Mailet APIs, but honestly, I didn't like the idea that to
use James, I had to embrace the Avalon server framework.
