Return-Path: 
 <users-return-45671-apmail-camel-users-archive=camel.apache.org@camel.apache.org>
X-Original-To: apmail-camel-users-archive@www.apache.org
Delivered-To: apmail-camel-users-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 653291024D
	for <apmail-camel-users-archive@www.apache.org>;
 Wed, 18 Dec 2013 20:13:30 +0000 (UTC)
Received: (qmail 40177 invoked by uid 500); 18 Dec 2013 20:13:29 -0000
Delivered-To: apmail-camel-users-archive@camel.apache.org
Received: (qmail 40145 invoked by uid 500); 18 Dec 2013 20:13:29 -0000
Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@camel.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@camel.apache.org>
List-Post: <mailto:users@camel.apache.org>
List-Id: <users.camel.apache.org>
Reply-To: users@camel.apache.org
Delivered-To: mailing list users@camel.apache.org
Received: (qmail 40137 invoked by uid 99); 18 Dec 2013 20:13:29 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Dec 2013 20:13:29 +0000
X-ASF-Spam-Status: No, hits=1.3 required=5.0
	tests=URI_HEX
X-Spam-Check-By: apache.org
Received-SPF: unknown (athena.apache.org: error in processing during lookup of
 francois.liot@poplidays.com)
Received: from [216.139.236.26] (HELO sam.nabble.com) (216.139.236.26)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Dec 2013 20:13:25 +0000
Received: from [192.168.236.26] (helo=sam.nabble.com)
	by sam.nabble.com with esmtp (Exim 4.72)
	(envelope-from <francois.liot@poplidays.com>)
	id 1VtNUN-00008Z-FG
	for users@camel.apache.org; Wed, 18 Dec 2013 12:13:03 -0800
Date: Wed, 18 Dec 2013 12:13:03 -0800 (PST)
From: fliot33 <francois.liot@poplidays.com>
To: users@camel.apache.org
Message-ID: <1387397583372-5745012.post@n5.nabble.com>
Subject: Aggregator, beyond the simple string example
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Virus-Checked: Checked by ClamAV on apache.org

Hi,

I really enjoy the pattern <enrich uri=3D"..." strategyRef=3D"..."/>
It's straight forward and really very reusable, really great.

Btw, beyond the StringInAggregatingStrategy documented example,
does anybody have a real life XML Aggregating Strategy example ?

Indeed, since, depending your endpoints, you do not control obviously the
encoding variables, either your body type, try to aggregate :
"""<?xml version=3D"1.0" encoding=3D"UTF-8"?><test1>content</test1>"""
with :
"""<?xml version=3D"1.0" encoding=3D"ISO-8859-1"?><test2>=C3=A9=C3=A8=C3=A0=
=C3=B9$=C3=AA=C2=A3=C3=AB</test2>"""

to obtain :
"""<?xml version=3D"1.0"
encoding=3D"UTF-8"?><xml><test1>content</test1><test2>=C3=A9=C3=A8=C3=A0=C3=
=B9$=C3=AA=C2=A3=C3=AB</test2></xml>"""
(encoded into utf-8)

This is slightly more complex than just :
    String oldBody =3D oldExchange.getIn().getBody(String.class);
    String newBody =3D newExchange.getIn().getBody(String.class);
    result =3D "<xml>" + oldBody + newBody + "</xml>";
    ...

I didn't get success trying to read newExchange as something else that a
"String.class", to get better Bytes level reading.

Thanks in advance for any advice.

Best regards,

Francois




--
View this message in context: http://camel.465427.n5.nabble.com/Aggregator-=
beyond-the-simple-string-example-tp5745012.html
Sent from the Camel - Users mailing list archive at Nabble.com.