Return-Path: 
 <users-return-57868-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 EE83417774
	for <apmail-camel-users-archive@www.apache.org>;
 Fri,  6 Nov 2015 08:06:35 +0000 (UTC)
Received: (qmail 12069 invoked by uid 500); 6 Nov 2015 08:06:35 -0000
Delivered-To: apmail-camel-users-archive@camel.apache.org
Received: (qmail 12022 invoked by uid 500); 6 Nov 2015 08:06:35 -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
Delivered-To: moderator for users@camel.apache.org
Received: (qmail 11173 invoked by uid 99); 6 Nov 2015 08:04:39 -0000
X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org
X-Spam-Flag: NO
X-Spam-Score: 2.314
X-Spam-Level: **
X-Spam-Status: No, score=2.314 tagged_above=-999 required=6.31
	tests=[KAM_LAZY_DOMAIN_SECURITY=1, URIBL_BLOCKED=0.001, URI_HEX=1.313]
	autolearn=disabled
Date: Fri, 6 Nov 2015 01:04:28 -0700 (MST)
From: SopwithInOut <singapore.sling@sharklasers.com>
To: users@camel.apache.org
Message-ID: <1446797068480-5773427.post@n5.nabble.com>
In-Reply-To: <1446534120084-5773337.post@n5.nabble.com>
References: <1446534120084-5773337.post@n5.nabble.com>
Subject: Re: How to read XML Payload
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I assume that by now, you will have already solved this. But in any case, I
would approach this with some kind of "/ Message Translator
<http://bit.ly/MTEIP>  /" solution in mind.=20

I'm very, very new to Camel. But I have a couple years experience using a
big-name proprietary ESB. I've done similar transformations using that ESB'=
s=20
"/ Message Translator <http://bit.ly/MTEIP>  /" support. The low-level
details are different. But at a high-level...

I would start off with some kind of reference to a single empty
"/PricePlans/Body/" node (/call it $mtBody, for short/). Then for each
<customer> I come across, I'd squirt each one in turn into my
previously-prepared /$mtBody/ node. In pseudo-code...


=09=09
Or assuming each of my /<customer>/ elements have some unique identifier =
=E2=80=94
maybe a "/custId/" attribute, say =E2=80=94 it should be possible to forego=
 a
looping approach. Instead, I could envisage some kind of  "/ Message
Translator <http://bit.ly/MTEIP>  /" that used XPath to somehow reference
each /<customer>/ by its /custID/ attribute.

How did you eventually solve it, by the way?





--
View this message in context: http://camel.465427.n5.nabble.com/How-to-read=
-XML-Payload-tp5773337p5773427.html
Sent from the Camel - Users mailing list archive at Nabble.com.