Thanks for making things more clear. I read the documentation and I
understand your point.
--
View this message in context:
http://camel.465427.n5.nabble.com/Exceptions-when-aggregating-messages-tp5735523p5735830.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Check out the Camel JMS page. Look for the transferExchane option.
Best,
Christian
Am 17.07.2013 07:19 schrieb "cristisor" :
> I'm afraid that I don't understand which option you are talking about. And
> how can I "care about the the property value which could not be
> serialized",
> please expla
I'm afraid that I don't understand which option you are talking about. And
how can I "care about the the property value which could not be serialized",
please explain in more details if possible?
Thanks.
--
View this message in context:
http://camel.465427.n5.nabble.com/Exceptions-when-aggrega
Did you enable the option to let camel-jms serialize the exchange?
You need to care about the the property value which could not be serialized if
that option is turned on.
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Bl
It seems that I was trying to serialize the exchange properties, which is
nonsense because the exchange that arrives on the new route will contain
it's own properties, and everything was failing probably when trying to
serialize the following property:
*CamelFileExchangeFile=GenericFile[path\filena
Hello and thank you for your reply.
This is the code for aggregating the whole camel message:
class ObjectsAggregationStrategy implements AggregationStrategy {
final Logger logger =
Logger.getLogger(ObjectsAggregationStrategy.class);
@SuppressWarnings("unchecked")
@O
Post your code if you could, and I can help take a look.
On Thu, Jul 11, 2013 at 7:42 AM, cristisor wrote:
> Hello,
>
> I'm trying to aggregate a bunch of messages, each containing a String as
> body, the In message from each exchange that comes to the aggregator, so
> that I can send only one
