I'm afraid you can do it with current version of camel-cxfrs, as we
don't put the cxf message into the camel message header when the
CxfRsConsumer get the request.
I just filled a JIRA[1] and will commit a quick fix for it shortly.
[1]https://issues.apache.org/jira/browse/CAMEL-4835
On Wed De
I'm not sure what kind of message that you send to multicast, but as
you are using the multicast, you need to make sure the message body is
re-readable.
You can enable the stream caching[1] to cache the stream.
[1]http://camel.apache.org/stream-caching.html
On Wed Dec 28 05:22:29 2011, ebinsi
Claus Ibsen-2 wrote
>
> For topics you need durable subscribers to ensure they receive the
> message.
> As the message will be discarded if sent to a topic with no active
> subscribers.
> Durable subscribers ensures the message will be stored, and send when
> the subscriber becomes active.
>
As
Hi, I am trying to use Zip / GZip data format to compress the output files
using Spring DSL implementation.
But looks like the files are not compressed. Not sure what mistake I am
making.
Appreciate your help.
Thanks & regards,
Ebe
--
View this message i
I want to extract data key/value data with an SQL query in a camel xml DSL
file and then use it later.
My thermometer reading app use case is this:
1. Once (or periodically): select thermometer,lowvalue from Thermometers
2. In Route A, read temperatures and put them in a topic
3. In Route B, in a
Apache Camel 2.8.3
Apache CXF 2.4.3
Spring 3.1.0-RELEASE
JDK 1.6.0_29
Is there configuration I can add to a cxfrs endpoint that allows access to the
HttpRequest to obtain the client IP address? Is there some other method to
obtain this information?
This seemed possible in olde
Hello all,
Suppose I have a method to expose via REST:
@GET
@Path("/doSomething")
public Response doSomething(@QueryParam("foo") String foo,
@QueryParam("bar") String bar) {..}
Then wired in Spring XML as:
Then added to a route as:
from("cxfrs:bean:so
In my project i am converting one message format to another. My route builder
contains following pseudo code -
from("source end point")
.policy(PROPAGATION_REQUIRED)
.processRef("inMessageDBWriter") //Write input message to Database
.processRef("processor1")
.processRef("processor2")
.agg
On Thu, Dec 22, 2011 at 11:46 PM, Mark Borner wrote:
>
> I'm trying to use Camel (v 2.6.0) JMS Request/Reply with Websphere 7 using
> Websphere MQ. I'm successfully able to put the request message onto the
> queue using the following URI:
>
>
> jms:queue:inboundQueue?connectionFactory=#connection
