Does the CouchDB driver configure work without the CamelContext element?
AFAIK the spring property holder can't work within CamelContext[1]
Not sure if the org.ektorp.spring.HttpClientFactoryBean has the spring
property holder.
[1]https://issues.apache.org/jira/browse/CAMEL-1066
Willem
On 12/
It's really a long answer for current solution of camel-cxf.
I think we can add a entry of in the camel message header to let people
access the CXFMessage contents from Camel message header.
That could be more easy to get the request remote IP by these same two lines
org.apache.cxf.Message cxfM
On 12/23/10 11:17 PM, serega wrote:
Willem.Jiang wrote:
Hi,
I don't think Camel support to add and remove the endpoints of the
LoadBalancer as you want in the runtime.
But the now camel route can be start and stop in the runtime. maybe you
can consider to stop the route, change the route and
That was sort of helpful Ashwin, thanks. Your long answer did get me to
explore the world of interceptors, but I am sorry to report that I still
don't see the remote IP address.
Here's what I did:
1) Create interceptors. I tried PRE_STREAM, but that didn't work so I just
created two more, one ea
All,
Has anyone had any luck using Ektorp's (CouchDB driver) Spring support in
Camel? I am having some problems configuring Ektorp as a Spring service.
Here is my Spring config:
--snip--
http://www.springframework.org/schema/beans";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-insta
On Thu, Dec 23, 2010 at 5:23 PM, Olivier.Roger wrote:
>
> The code is now cleaned and migrated to 2.6 (was 2.4) for donation.
> A patch will be provided in the first days of 2011.
>
Ah perfect. Glad you got OK from your company to donate it.
The Camel community continues to kick ass!
> Olivier
Hi
I created a ticket
https://issues.apache.org/jira/browse/CAMEL-3458
And implemented a fix for this.
On Tue, Dec 21, 2010 at 12:49 PM, mikaelfj wrote:
>
> I'll add a jira for it - so far we are ensuring the strings are of proper
> length before setting them on the annotated class.
>
> I don'
The code is now cleaned and migrated to 2.6 (was 2.4) for donation.
A patch will be provided in the first days of 2011.
Olivier
--
View this message in context:
http://camel.465427.n5.nabble.com/Aggregator-Persistence-tp2800301p3316667.html
Sent from the Camel - Users mailing list archive at Na
I"ll update the ticket 3228 to show the dozer team is still working through
these issues.
Are you guys (Dozer) going to be merging the dozer and dozer-osgi baselines?
--
View this message in context:
http://camel.465427.n5.nabble.com/Issue-with-camel-dozer-tp3315547p3316665.html
Sent from the
On CXF side, you can access headers like this:
import org.apache.cxf.message.Message;
Message cxfMessage;
Map> cxfHeaders =
(Map)cxfMessage.get(Message.PROTOCOL_HEADERS);
List values = cxfHeaders.get("myheader");
On 12/23/2010 09:54 AM, Aki Yoshida wrote:
Hi,
I am trying to pass the Camel
Willem.Jiang wrote:
>
> Hi,
> I don't think Camel support to add and remove the endpoints of the
> LoadBalancer as you want in the runtime.
> But the now camel route can be start and stop in the runtime. maybe you
> can consider to stop the route, change the route and start it again.
>
Can y
Create a JIRA ticket and provide a test case if possible.
Also we love contributions, so if you have the chance peek in the source and
try to provide a patch which fixes the issue
http://camel.apache.org/contributing.html
--
View this message in context:
http://camel.465427.n5.nabble.com/Stream
Recipient List EIP also has an AggregationStrategy you can set and use to
determine what to send out from the it.
--
View this message in context:
http://camel.465427.n5.nabble.com/problems-with-Aggregator-tp3316379p3316573.html
Sent from the Camel - Users mailing list archive at Nabble.com.
On Thu, Dec 23, 2010 at 8:34 AM, frankie_hr
wrote:
>
> Hi,
>
> Thank you for your reply! That sure makes sense and explains why I wasn't
> able to get the header.
>
> However, is there any other way to tell whether it's the last redelivery
> from within the redelivery processor? You suggested to r
On Tue, Dec 21, 2010 at 7:29 PM, Pavel wrote:
> Cool; I guess then for this topic I'm missing a review from core committers
> (Gert, are you around?), so that I could address feedback. And propose docs
> then.
>
> IMO the next logical and handy DSL enhancement would be introduction of
> "every(per
Hi,
I am trying to pass the Camel headers to the CXF component, but
somehow I am having trouble. For example, when I use the following
configuration:
myvalue
I thought this header would be placed somewhere in the CXF message so
that I could access it
Hi,
Take a look at dataset component http://camel.apache.org/dataset.html and
SimpleDataSet class, expecially at its "size" property.
Regards,
Sergey
klausb
23.12.2010 15:35
Please respond to
users@camel.apache.org
To
users@camel.apache.org
cc
Subject
Is there a concept for a one-shot m
Is there a concept (route-element) to create a one-shot message exchange?
That is a route that sends just a single exchange, if the route is started
(typically, when the enclosing OSGi comp starts).
Right now I do this with a timer and a final processing step, that stops the
timer route. This is
Hi,
Camel normally store the security context[1] into the exchange, if you
want to the jaxws-handler access these kind of information you can
consider to copy this information into the CXF message instead of store
it as thread local.
As you know camel is an async route engine[2], you can't gua
19 matches
Mail list logo
