I'm seeing a behavior in camel 1.6 I don't understand. when I used the
producerTemplate to kickoff a workflow that
includes a @RecipientList component I seem to get back the result of the
recipient list... but my other services
end up being called (and their results simply lost to the ether).
Looking into this more it seems to be because I am ending up in a
BeanProcessor. Line 120 of the bean processor is where the output of the
@RecipientList method is overwriting the Out part of the exchange (which
actually has the right data in it at that point).
Using the Spring DSL is there a
In Camel 1.5 when using the ExchangePattern.InOut I get an exception
when tearing down the activemq broker the exception occurs no matter how
the thread is stopped. Is there configuration to allow the InOut pattern
to work without causing exceptions when the broker is shut-down? The
exception
I submitted a fix. Restlet component now checks for
Exchange.isFailed() and looks at Fault message to prepare a response
when isFailed() is true. It is consistent with HTTP component.
https://issues.apache.org/activemq/browse/CAMEL-1400
On Thu, Feb 26, 2009 at 10:55 AM, William Tam
The Timer or Quartz components and DSL as in: from(timer://foo?period=6)
appear to generate NoClassDefFoundError and ClassNotFound exceptions for
unrelated components, such as Scala, Mina, Http,etc. There are also many
warnings with org.apache.camel.util.ResolverUtil addIfMatching. The
On Fri, Feb 27, 2009 at 6:07 AM, skappel skap...@finobra.com wrote:
The Timer or Quartz components and DSL as in: from(timer://foo?period=6)
appear to generate NoClassDefFoundError and ClassNotFound exceptions for
unrelated components, such as Scala, Mina, Http,etc. There are also many
