> 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
Ajay Chitre wrote:
Hello,
We are developing a business application based on James for which we are
considering the following architectural ideas/rules:
1) Do not put any business logic in the Mailets, for the same reason as why
we don't put any business logic in the Servlets.
2) When a Mailet
Hello,
We are developing a business application based on James for which we are
considering the following architectural ideas/rules:
1) Do not put any business logic in the Mailets, for the same reason as why
we don't put any business logic in the Servlets.
2) When a Mailet is called, it will p
