Great, we've needed that for a long time now :-) AFAIK, the spring mail support uses the Javamail api. Is there anything that the endpoint based on spring could not do wrt to the other one ?
Also wrt to velocity and other templating frameworks, it might we worth having a look at camel. I would even consider using camel mail support (http://activemq.apache.org/camel/mail.html) directly, because camel already support templating: http://cwiki.apache.org/CAMEL/templating.html Given that camel supports JBI, we could consider mail endpoints using a camel route: from("jbi:xxx"). to("velocity:com/acme/MyResponse.vm"). to("smtp://host:port/") Just some thoughts.... On Tue, Feb 26, 2008 at 10:04 PM, lhe77 <[EMAIL PROTECTED]> wrote: > > Hi, > > actually I am developing a JBI compliant binding component for polling and > sending emails. > I will start here a discussion to put together all ideas and requirements > for this BC. So any > suggestion is welcome. > > State: > - The BC uses the JavaMail API to poll and send emails. (2 endpoints for > now) > > ToDo: > - Sending mails via spring mail. (via another endpoint) > - integrate frameworks like Velocity for email template handling > > Regards, > Lars > > -- > View this message in context: > http://www.nabble.com/new-JBI-componten%3A-EMail-BC---Discussion-thread--tp15699972s12049p15699972.html > Sent from the ServiceMix - Dev mailing list archive at Nabble.com. > > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/
