Do the component developers follow this list? I'd love to see a switch as
well. Issue tracker for components ?
On Wed Nov 26 2014 at 1:44:01 AM Claus Ibsen wrote:
> Hi
>
> Did you get in contact with the xmjson team about the issue and if
> they are willing to add a flag to turn this on/off etc?
Hello All,
Sorry if this is a newb question but I was wondering if there is a way to
test my routes in way that does not involve added .to("mock:xxx") on the
end of the routes. I may be pure vanity but I don't like the idea of having
"production" routes with mocks in them. I saw the documentation
Ok, I was able to "append" a "mock:result" to a route using
weaveById("silver").after(), still seems a little clunky though:
https://gist.github.com/vinny2020/616935f45d34fb6b8dbd
On Wed Jan 28 2015 at 3:08:05 PM Vinny wrote:
> Hello All,
> Sorry if this is
Hello All,
Am I correct i assuming that the normal Camel HTTP headers are not
populated when we use the netty4-http component? To access things like the
query string we need to do it using Netty tools like QueryStringDecoder on
the FullHttpRequest object. Just wanted to make sure I didn't configur
Hello,
Trying to test some of my nmr routes. I've looked at
http://camel.apache.org/nmr.html
and have looked at the test example at the bottom. The problem is I can't
seem to locate the dependency that supplies the AbstractComponentTest class
anywhere. Is there a maven dependency that is needed? Is
gt; Only if you use JBI alot and can't drop that old s*** then you are
> stuck on it. If not then move on to just Camel.
>
> On Tue, Jul 14, 2015 at 6:31 PM, Vinny wrote:
> > Hello,
> > Trying to test some of my nmr routes. I've looked at
> > http://camel.apache
