Re: HTTP transport

[moodboom <mo...@gmail.com>]

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.

Re: HTTP transport

[moodboom <mo...@gmail.com>]

dejanb wrote
> Hi,
> 
> there's a difference between Camel http component and ActiveMQ http
> transport. Both are solid for what they've been designed to do.

Thanks dejanb, and a huge thanks for all the mailing list answers over the
years, they've helped me get started.

Can I ask for a quick nudge on my problem?  I just want the simplest way to
automatically process a queue, sending messages that arrive back out to a
RESTful provider.  I assume that means I need Camel, right?  Is there a
working example of a Camel route that send to an HTTP provider?

Thanks,
Michael



--
View this message in context: http://activemq.2283324.n4.nabble.com/HTTP-transport-tp4014555p4669713.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: HTTP transport

[Dejan Bosanac <de...@nighttale.net>]

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
dbosanac@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 <mo...@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.
>