[prev in list] [next in list] [prev in thread] [next in thread] 

List:       james-user
Subject:    Re: Application architecture for a James based solution
From:       "Danny Angus" <danny () apache ! org>
Date:       2008-07-24 16:10:35
Message-ID: 5ec229170807240910p1a7023c6re262419bdebdca24 () mail ! gmail ! com
[Download RAW message or body]

> 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: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org

[prev in list] [next in list] [prev in thread] [next in thread]