You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Donald Whytock (JIRA)" <ji...@apache.org> on 2011/06/28 21:18:17 UTC
[jira] [Updated] (CAMEL-4161) make camel-mail dependency on
Spring's JavaMailSenderImpl optional
[ https://issues.apache.org/jira/browse/CAMEL-4161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Donald Whytock updated CAMEL-4161:
----------------------------------
Attachment: MimeMessagePreparator.java
JavaMailSenderImpl.java
JavaMailSender.java
Attached is a sample set of files that implement a bare minimum of functionality for sending mail. These worked with my testing of changes to camel-mail.
> make camel-mail dependency on Spring's JavaMailSenderImpl optional
> ------------------------------------------------------------------
>
> Key: CAMEL-4161
> URL: https://issues.apache.org/jira/browse/CAMEL-4161
> Project: Camel
> Issue Type: Improvement
> Components: camel-mail
> Reporter: Donald Whytock
> Priority: Minor
> Attachments: JavaMailSender.java, JavaMailSenderImpl.java, MimeMessagePreparator.java
>
>
> camel-mail is currently dependent on org.springframework.mail.javamail.JavaMailSenderImpl, but uses relatively little of its functionality. In many cases it may be sufficient to fall back on a default JavaMailSenderImpl that only implements the bare minimum necessary to send mail, similar to how Management functionality falls back on DefaultManagementStrategy if the Spring JMX implementation is not available.
> This would make camel-mail use possible in an otherwise Spring-less application.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira