That would be great. Expanding the example a bit to include some injected
components would be nice, assuming that is possible (or making it possible
if not).

--Tim


Claus Ibsen-2 wrote:
> 
> Hi
> 
> I think James Strachan can shed lights on the camel-guice as he build it.
> I am sure there are some features missing in this component so we can
> use help to improve it.
> 
> 
> On Wed, Nov 25, 2009 at 6:50 PM, mumbly <mcner...@gmail.com> wrote:
>>
>> I've been taking a look at using Camel with Guice for DI, but I'm having
>> a
>> little trouble understanding exactly what the integration provides. I've
>> got
>> the configuration aspect and that seems to work fine. But it is unclear
>> to
>> me if/how to work with Guice enhanced components. Specifically, if I am
>> using a bean component which uses @Inject, it doesn't appear that the
>> bean
>> is being pulled from the Guice context (in other words, the other
>> components
>> aren't being injected).
>>
>> I'm new to both Camel and Guice, so I could be missing something obvious
>> here or there may be another pattern for DI using Guice with Camel that I
>> missed. So I guess my basic question is does the Camel/Guice integration
>> provide the ability to inject components within the routing chain? with
>> the
>> bean component?
>>
>> I see in the Guice example included in the dist, but it only seems to
>> deal
>> with using Guice for configuration of the routes.
>>
>> --Tim
>> --
>> View this message in context:
>> http://old.nabble.com/Using-Guice-with-Camel-tp26517323p26517323.html
>> Sent from the Camel - Users mailing list archive at Nabble.com.
>>
>>
> 
> 
> 
> -- 
> Claus Ibsen
> Apache Camel Committer
> 
> Author of Camel in Action: http://www.manning.com/ibsen/
> Open Source Integration: http://fusesource.com
> Blog: http://davsclaus.blogspot.com/
> Twitter: http://twitter.com/davsclaus
> 
> 

-- 
View this message in context: 
http://old.nabble.com/Using-Guice-with-Camel-tp26517323p26532525.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Reply via email to