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 suppose the main reason I haven't simply embraced James is its reliance on the now-defunct Avalon project. I cringe at the thought of introducing yet-another server framework into my development and production environments! J2EE, for all its flaws, is well known, mature, stable, and very well documented/supported. I've been monitoring the JBoss effort, but am not at all clear that it's not going to ask me to don a different style straight jacket than James wants me to wear. The talks about relying on BeanShell or JavaScript to process e-mails handled by my Java-based e-mail server is an example of such a straight jacket. To more fully discuss these issues, I'm posting a new topic on "What I'm Looking For, And Not looking For, In A Java-Based Enterprise E-mail Server" Jack View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3869952#3869952 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3869952 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-Development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-development
