> I am assuming this is a fairly standard architecutre. Any pros/cons? Any > other ideas?
Alternatively you could package the information from the mail object into a JMS message,publish it to a queue acessable by a J2EE server and have it handled by a Message Driven Bean, this can be useful when you want to incorporate email into a J2EE system, because it lets you use James as the gateway, but keeps all of your processing logic in your J2EE applications. d. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
