Hello-
Please let me know if this is not the right forum for this. I don't
want to take anyone here away from developing too long, but...
I have downloaded and installed James 1.0 which appears to be in
beta stage. I am looking into integrating James into our web-based
app to add mail list functionality and it looks like a good candidate.
I did have some questions and concerns (I realize the answers to these
might not exist).
On the technical front: it appears that if a mailet's 'service' method
returns a null Mail object, we kick-out of the pipeline. Is this
desired behavior? One of the things that stuck me for a bit was the
Delivery Mailets return a null Mail object. Why is this so? What if
I have multiple mailets that deliver to different places? From the
newsgroup, it appears the API in the next rev will be:
void service(Mail mail) throws MailetException;
Will the spool manager still catch and log all exceptions and continue
down the pipe with the original Mail object? (Obviously I'm not voting
or anything, but I like this approach better). Did the setState
proposal pass?
On the business side: from the newsgroup, it looks like the
configuration
approach and the mailet api is undergoing recent rework, but things
appear to be winding down. Any timeline when that work will
be done? Any timeline on when James as a product will be ready for
General Availability? Would anyone here deploy James 1.0 in a full
production environment?
I appreciate all the work people have done on this and look forward
to using James.
Thanks,
-Tom Casaletto
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/>
Problems?: [EMAIL PROTECTED]
