Re: How can i use CDI with the Camel Context

You should really review some of the available example. This one: camel-example-spring might help. Also, a review of Spring basics sounds like it would be helpful. -- View this message in context: http://camel.4654

Re: Mail-Component: HTML body is sent twice.

It has been my experience that the Mail component will try to add all headers in the headers map as email headers. I generally remove any unnecessary headers from the org.apache.camel.Message before invoking the Mail component. -Jason -- View this message in context: http://camel.465427.n5.na

Re: State of the camel-cdi component

That is great news! Thank you for responding. --Jason -- View this message in context: http://camel.465427.n5.nabble.com/State-of-the-camel-cdi-component-tp5760578p5760587.html Sent from the Camel - Users mailing list archive at Nabble.com.

State of the camel-cdi component

Will the Camel project will officially adopt: https://github.com/astefanutti/camel-cdi as its CDI extension. I have experimented with the 'official' extension available in 2.14.0 and feel that it is lacking much of what it needs to a viable component where as https://github.com/astefanutti/camel

Re: ProducerTemplate null when used to construct bean in new JndiContext in a unit test

I figured it out. My answer can be found here: http://stackoverflow.com/questions/25851033/producertemplate-null-when-used-to-construct-bean-in-new-jndicontext-in-a-unit-t

ProducerTemplate null when used to construct bean in new JndiContext in a unit test

I am trying to unit test a route that uses bean to dynamically construct an sftp endpoint. This works when I run my route in a normal context, as it seems a template is already in the registry and can be correctly injected. My problem is when trying to construct the unit test I seem to be runnin