I created this as a proposal as I expected some disagreement along the way :)

In my view changing from the Mailet container taking care of managing resources to placing the responsibility on the Mailet developer is a retrograde step that is unnecessary to achieve our objectives.

It also exposes the possibility for dispose() to be invoked inappropriately against Mail instances passed into the Mailet Container.

We would be destabilising much to achieve very little. What is so wrong with the proposed closure style solution I made earlier?

Cheers
--Steve

On 19/12/2011 10:04, Steve Brewin wrote:
Discussion moved over from James Dev as per Stefano's suggestion.
-------- Original Message --------
Subject:     Re: [mailets] Proposal: MailetContext enhancement
Date:     Sun, 18 Dec 2011 20:25:53 +0100
From:     Norman Maurer <norman.mau...@googlemail.com>
Reply-To:     James Developers List <server-...@james.apache.org>
To:     James Developers List <server-...@james.apache.org>
CC:     server-...@james.apache.org <server-...@james.apache.org>



I dont agree with you here... I think just have an dispose method is fine. Its not different the for example the need to close an EntityManager which is quite nature in the enterprise.

bye
norman

Von meinem iPad gesendet

Am 18.12.2011 um 19:45 schrieb Steve Brewin<sbre...@synsys.com>:

Obviously this was my first thought, but this exposes the mail server to compromise by Mailets that forget to call dispose() on failure.

If we want to be Enterprise strength, this isn't good enough as it is too weak a contract. We must guarantee that dispose will be called (my new solution), or prevent the exposure (the current solution).

 --Steve

 On 18/12/2011 18:56, Norman Maurer wrote:
I would prefer more to just add a dispose() method to the Mail interface.

 Bye,
 Norman



 - - - - - - - - - - - - - - - - - -

This private and confidential e-mail has been sent to you by Synergy Systems Limited. It may not represent the views of Synergy Systems Limited.

If you are not the intended recipient of this e-mail and have received it in error, please notify the sender by replying with "received in error" as the subject and then delete it from your mailbox.

 ---------------------------------------------------------------------
 To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
 For additional commands, e-mail: server-dev-h...@james.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org





Reply via email to