Alan D. Cabrera wrote:
I don't think that generally speaking one solution is always better
than the other and I didn't analyze the specific "dispose" methods in
James.
I see at least some big issue to not do the change:
- backward compatibility
I'm curious, does this statement assume that others have embedded James?
Just an example:
Mail interface is part of the mailet apis. If we add "dispose()" to the
Mail interface everyone implementing its own Mail object will have to
change the objects.
Btw, this is not a big issue if we plan to do this kind of refactorings
for 3.0, but I think there are many similar changes if we start moving
such methods to our business interfaces and I'm not sure this is a good
move.
As a news: Mailet APIs are used by third party projects like MailCatcher:
http://developer.spikesource.com/projects/mailcatcher/
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
