@arno noordover : Sorry did not get exactly what you meant. Are you
suggesting I have to give complete URL in "CamelHttpUri" header instead of
using header variables like ${header.employeeName}?
--
View this message in context:
http://camel.465427.n5.nabble.com/java-lang-IllegalStateException-u
Are you suggesting to use "https" (Http Client 3.x) instead of "https4" (Http
Client 4.x)?
I have already tried it and https4 fails. Thats the error I have mentioned
in the thread.
--
View this message in context:
http://camel.465427.n5.nabble.com/java-lang-IllegalStateException-unsupported-pro
Hi Steve,
Thanks a lot, very helpful! I now can see the result in my
JoinReplyAggregationStrategy that two message have merged when I debugged
it. But after setBody to exchangeOld, it returns nothing. It seems get
nothing after aggregate...
Here is the strategy:
public class JoinReplyAggregation
Thanks Jim for looking into this. Confirmation that it's broken vs something
I'm doing wrong is a big time saver. Will check back in on the next release.
The 'camel-websockets' package works for me to a certain degree but opens up
multiple random ports per client connection making it completel
You have two things:
1. the uri-attribute in the to-element;
2. the "CamelHttpUri" headers.
Both have a "protocol" prefix. The "protocol" prefix in de uri-attribute is
used to select the component you want to use.
When using the "CamelHttpUri" to override the URL that gets determined in
the compon
I tried the 2.18.0 state packages, but had compile errors. Decided to wait
for 2.18.1 before trying to resolve problems
On Fri, Oct 28, 2016, 8:55 PM Ingram, Stuart wrote:
> Thanks Claus! I wasn't aware of the *-starter packages for Camel. Much
> appreciated for the pointer.
>
> Moving to the
I am not using the scala dsl. It is basically java in scala.
My fault. I meant to say:
def configure(): Unit = {
from("activemq:TEST.FOO")
.to("stream:out")
}
But I found my mistake; my producer was sending buffered messages and
camel was doing the right thing.
On 30.10.
I am not familiar with the scala dsl but if you just want to log the
message you can write:
.log(LoggingLevel.INFO, "mylogger", "${body}")
If you want to send to stream out then can do:
.to("stream:out")
You will need to add the dependency for camel-stream for this work.
On Sun, Oct 30, 2016 at
Check your queue. You might find that the messages are not consumed and thus
stay on the queue.
> On 30 Oct 2016, at 12:43, Simple Appointment wrote:
>
> I am new to camel and would like to use it as our integration component.
> I was trying to log messages received from a jms queue to the co
I am new to camel and would like to use it as our integration component.
I was trying to log messages received from a jms queue to the console
and it seems that the messages accumulates. Lets say I have messages
one,two,three,four in my queue.
def configure(): Unit = {
from("activemq:
Thabks for the response.
The problem is that I have to do something
from direct foo
to bean pre process
recipient list *process message for each endpoint in recipient list and
then process response from each end point and then aggregate all responses*
to bean post process
I don't kno
11 matches
Mail list logo
