Tim Stephenson wrote: > > The original and simple idea of using JMS as a means to inject Mail > into James' processors seems good to me, it would open up James to the > JEE audience. I was about to embark on the exact same experiment, so > thanks Robert. > > The source of the message can be the James SMTP service, Fetchmail or > any number of other things and internal Mail processing downstream is > unaffected. This introduces a break between the mail source and the > mail processing, which surely is a good thing? >
Please excuse the plug, but have you seen Apache Camel? Its a little integration framework inside the ActiveMQ project. Its ideal for consuming messages from somewhere, transforming them and sending them on some place. For example using the Message Translator pattern... http://cwiki.apache.org/CAMEL/message-translator.html It also supports a ton of other Enterprise Integration Patterns... http://cwiki.apache.org/CAMEL/enterprise-integration-patterns.html So you could consume from any of these transports and protocols (including JMS) and send to JAMES (or vice versa)... http://cwiki.apache.org/CAMEL/components.html So whether its flat files, Atom, FTP, HTTP, JMS, IRC, XMPP or whatever - it wouldn't really matter to your code - instead you just focus on the actual integration & transformation etc. You can use camel-core.jar in any IoC framework; the only glitch is the JMS support in Camel currently reuses Spring's JmsTemplate / MessageListenerContainer and declarative transactions - I'm not too sure how easy it is to mix Spring and Phoenix. -- James ------- http://macstrac.blogspot.com/ Open Source Integration http://open.iona.com -- View this message in context: http://www.nabble.com/ActiveMQ-tp14037280p14269089.html Sent from the James - Dev mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
