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).
Her
Hi Todd,
Thanks for your feedback. Fault handler of Restlet component should
be consistent with other components. It sounds like it isn't. Let
me look into it.
Cheers,
William
On Mon, Feb 23, 2009 at 7:21 PM, tfredrich wrote:
>
> I'm utilizing the Restlet component (via a Trunk build) and a
Hi,
I would like to have the opinion of the camel riders regarding to the
following point.
When you work with messages that you have to unmarshall/marshall, it occurs
frequently that you have to change how you parse or format your message
because the specifications have changed (e.g. FIX 4.1 --
Hi,
No. There is no simple way to do this unless you do this using something
like
from("SourceURL").
filter().method("myBean", "isAtrributeQueue13or14").
to("TargetURL");
Obviously you will need to parse the payload and determine whether the queue
attribute is 13 or 14.
Yo
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 way
On Thu, Feb 26, 2009 at 6:45 PM, paquettd wrote:
>
> 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
Hi David,
This is not possible without adding a processor behaving like a payload
transformer/replacer. The way to do this is
http://camel.apache.org/schema/spring";>
In myBodyReplacementProcessor
public class MyBodyReplacementProcessor implements Proces
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 recei
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 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
warnings with org.apache.camel.util.ResolverUtil addIfMatching. The timer
On Fri, Feb 27, 2009 at 6:07 AM, skappel 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
> warnings with or
11 matches
Mail list logo
