I don't suggest your start the ActiveMQ Broker (Using TCP transport) with Guice in the same time you start up the Camel Context. If you have multi Camel Contexts which share same ActiveMQ broker, that will cause some troubles.
How about to write a ActiveMQ Module to wrap the start and stop methods of the ActiveMQ broker in Guice? Willem adambender wrote: > I am working on a project with heavy Guice integration and we are now > developing a messaging system and have decided to go with > ActiveMQ+Camel+Guice. I have a good understanding of the producer, consumer > and JMSComponent injection, but I haven't been able to figure out the Guice > way of bringing up a Broker. The examples and tests use the vm transport so > the Broker gets started for free... I need to start a broker using the TCP > transport. anyone have any examples or suggestions about how to start an > ActiveMQ Broker using Guice? > > Thanks, > Adam
