Tom Casaletto wrote:
>
> 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?
Yes.
> One of the things that stuck me for a bit was the
> Delivery Mailets return a null Mail object. Why is this so?
Becouse after beeing delivered the mail do not need any futher
processing and so must go out of the pipe.
> What if
> I have multiple mailets that deliver to different places?
if (recipent == *@mydomain.com)
servlet=deliverToMyDomain
if (recipent == *@yourdomain.com)
servlet=deliverToYourDomain
....
you have to split the mail and have one different Mail for each
"different place".
> 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?
Yes. On any exception the spool manager will split the processing tree
and send the Mail to a special mailet defined in conf to manage errors
(like ToRepository or Null ...).
A specific mailet (or pipe processing) can be written that takes the
state and the error message and perform specific task (notify admin,
bounce back, destroy, ...).
>
> 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'm going to code the "void service(Mail)" today and I hope this is the
last big change.
-My timeline for 1.0 (probally will be called differently) is JavaOne (5
June).
-The company I'm working for are planning to use James as a piece of
their product.
>
> I appreciate all the work people have done on this and look forward
> to using James.
Thanks
>
> Thanks,
>
> -Tom Casaletto
>
Fede
P.s. Are you italian? Half the people working on James are italian....
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/>
Problems?: [EMAIL PROTECTED]
