Hi Stephane,
I just took a quick stab and it works with the following route, note the
endpoint is the url with netty4 prefixed.
@Override
protected RoutesBuilder createRouteBuilder() throws Exception {
return new RouteBuilder() {
@Override
public void conf
Hi,
I went through the whole thread, but didn't find out how the
camel-netty4-http endpoint is used (from the camel route).
I guess that something is still missing.
Willem Jiang
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang
Weibo
Good evening Claus,
Thank you for your swift reply.
In fact, I have omitted to say that I already turned on the stream caching
(my fault, I work hard 7/7, please forgine me), by doing this:
getContext().setTracing(true);
getContext().setStreamCaching(true);
Hi
netty is streaming based, and you also do a wire tap, so the body is
only readable once. You need to turn on stream caching
See this FAQ and its links for more details
http://camel.apache.org/why-is-my-message-body-empty.html
On Sun, Feb 5, 2017 at 2:33 PM, scoutant wrote:
> Hello,
>
> I'm
It seems that using MockEndpoints in spring boot tests you can get
unpredictable results.
Unit tests annotated with ->
@RunWith(CamelSpringBootRunner.class)
@MockEndpoints
Seems to work when running them locally, but fails on CI servers properly
due to somewhat slower execution time.
The proble
Hello,
I'm developping a payment platform and I decided to use Camel EIP 2.18.0 as
my communication framework. In particular the Netty HTTP4 component. Note
that I'm new to Camel.
I have a problem using Netty HTTP4 while requesting a simple web service
published by the European Central Bank to ge
