Thanks for fixing, I didn't try it out because I think I cannot use a
snapshot version. But I used enrich as you proposed so now I can send emails
with an attachment :). Is there a reason to use a "direct" endpoint in
between, instead of using the stringtemplate endpoint directly in the enrich
method?
Christian Mueller wrote
>
> I had to fix camel-stringtemplate, camel-freemaker and camel-velocity in
> all supported branches (trunk, camel-2.9.x, camel-2.8.x and camel-2.7.x).
> If you cannot use a snapshot version (what I asume), I would propose to
> use
> the enricher component as a workaround. Something like:
>
> from("xxx")
> .enrich("direct:workaround", aggregationStrategie)
> .to("smtp:XXX"");
>
> from("direct:workaround")
> .to("stringtemplate:XXX");
>
> And the aggregation strategie can copy the attachment from the old
> exchange
> to the new one.
>
> Sorry for this inconvenience. Let me know if you need help here.
>
> Best,
> Christian
>
--
View this message in context:
http://camel.465427.n5.nabble.com/How-to-send-a-templated-mail-with-attachment-tp5125167p5133615.html
Sent from the Camel - Users mailing list archive at Nabble.com.
