Hi, there's a difference between Camel http component and ActiveMQ http transport. Both are solid for what they've been designed to do.
Regards -- Dejan Bosanac ---------------------- Red Hat, Inc. FuseSource is now part of Red Hat dbosa...@redhat.com Twitter: @dejanb Blog: http://sensatic.net ActiveMQ in Action: http://www.manning.com/snyder/ On Wed, Jul 24, 2013 at 5:18 AM, moodboom <moodb...@gmail.com> wrote: > Jason did you arrive at a compact way to include http support? > > Sorry to revive this old thread, but it seems relevant to my problem. I'm > new to this, using a pretty vanilla ActiveMQ config with a camel route, and > getting "No component found with scheme: http4". > > So I'm wondering what the minimal is I have to do to enable http route > targets. Apologies, it might be a basic question but I'm very new to this, > appreciate any help. > > Jason Dillon wrote > > If there are folks using this in production, then why isn't this feature > > in its own module and not lumped together with all the other fluff in > > activemq-optional? > > > > I have ~12 dependency excludes when depending on that module to keep out > > unwanted/unused stuff which is needed by other "optional" features > > provided by that module. > > > > :-( > > > > --jason > > > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/HTTP-transport-tp4014555p4669671.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
