I was leaving a bit out.
It already is split into two routes like you suggest. I've tried
doing the inOnly trick as well. I'm using the scala DSL, so I had
something like:
A --> B inOnly --> seda:a
seda:a -> log
It used to do exactly what you say until we upgraded to Camel 2.2 (via
a Fuse upgr
K, I'll try that, but I thought the seda component could did this
automagically. What does waitForTaskToComplete=Never mean?
Thanks.
On Thu, Jul 1, 2010 at 10:57 PM, Claus Ibsen wrote:
> On Thu, Jul 1, 2010 at 11:27 PM, crankydillo wrote:
>> Hi,
>>
>> We are processing HTTP requests with a rou
Hi,
I have the following Scala DSL route defined:
when (...) {
process(...)
--> (...)
--> (...)
} otherwise {
process(...)
--> (...)
}
For various reasons, I need to implement this with a Java DSL route,
but I can't figure out how to nest multiple statements. All the
examples I s
Hi,
I've created a black-box request/response facade around a Camel route. Think:
class BlackBox {
function process(request: Request): Response
}
This thing lives in a spring environment and is getting the
CamelContext injected. For each blackBox call, I use the context to:
1. Lookup an end
Hi,
We're using Camel 2.6.0 in Fuse 4.3. We have a Camel route that
exposes a bean method as a vm endpoint. I'm trying to test this route
with PaxExam 2.2.0. When I send an exchange to it, it always times
out. I have put breakpoints in the bean method, but they never get
hit. It hangs in Seda
22 AM, Willem Jiang wrote:
> Can you show us the camel context configure ?
> Is there any sead consumer defined in the route ?
>
> On Wed Aug 31 18:55:47 2011, Samuel Cox wrote:
>>
>> Hi,
>>
>> We're using Camel 2.6.0 in Fuse 4.3. We have a Camel route that
&
I don't know what I did, but it's working now. I'll take it, but I'm
not a big fan of that;)
On Wed, Aug 31, 2011 at 7:52 AM, Samuel Cox wrote:
> I'm thinking this is not what you want, but here is the declaration of my
> route:
>
>
>
>
Hi,
I'm trying to define a route specific exception handling mechanism.
It's purpose is to apply a custom format to the response body of an
HTTP response. My route is:
java.lang.Exception
true
I should have specified the version... We're using Camel 2.6.
On Fri, Feb 3, 2012 at 10:16 AM, Samuel Cox wrote:
> Hi,
>
> I'm trying to define a route specific exception handling mechanism.
> It's purpose is to apply a custom format to the response body of an
&g
A changed all the to-uri pairs to process-ref pairs. The behaviour
appears to be the same.
On Fri, Feb 3, 2012 at 10:46 AM, Babak Vahdat
wrote:
> Hi
>
> a xyzProcessor can't be referenced as a URI inside a Route because as the
> name already says it a Processor. So that changing those:
>
>
>
>
We're using camel-servlet. Here is the exception that is ultimately
exposed the HTTP client:
org.apache.camel.ExchangeTimedOutException: The OUT message was not
received within: 1 millis. Exchange[Message: [Body is null]]
at
org.apache.camel.component.seda.SedaProducer.process(SedaProduc
My colleague and I were just talking about how I didn't give enough
information...
The httpToServicesProcessor uses an injected ProducerTemplate to fire
off an exchange to another route...
I have since determined that is somehow involved in the problem. When
I simply threw an exception from the
On 2012-02-03 4:58 PM, Babak Vahdat wrote:
Instead of using a ProducerTemplate it would be much easier to do a to("...")
to fire an exchange into your second route inside the same camel context.
Those were my exact words to my colleague:) He told me that the
separate ProducerTemplate was used
13 matches
Mail list logo
