I think we should also remove the 3 methods. They are provided by the MailetContext interface too. This mean that if someone created a block that depend on MailServer for this operation simply should change the block definition adding MailetContext dependency (it is the same "James" object) and adding the lookup for that object.
Removal of the 3 methods will remove apparent deprecate method usage in James.java: we implement the methods that are defined both by MailServer and MailetContext interfaces and deprecating them from MailServer make James.java compilation to send warning about deprecation. I suggest the use of SpoolRepository.store instead of MailetContext.sendMail or MailServer.sendMail to link components. SpoolRepository is an easy interface that could "easily" be implemented by JMS providers or similar. Stefano > Author: bago > Date: Sat Aug 20 09:35:34 2005 > New Revision: 234093 > > URL: http://svn.apache.org/viewcvs?rev=234093&view=rev > Log: > Deprecated unused sendmails from MailServer. We provide this > methods via the MailetContext service (JAMES-412) We > could/should also remove this methods instead of deprecate them. > > [...] > Modified: > + * > + * @deprecated You can use MailetContext service for this purpose > */ > void sendMail(MailAddress sender, Collection recipients, > MimeMessage msg) > [...] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
