Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: pass (nike.apache.org: domain of claus.ibsen@gmail.com
 designates 74.125.83.173 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type:content-transfer-encoding;
        b=Hg0XEvRkdgiQvk25/ybtYHmDz1Sb32yrDg6OYUx7oaFpVYTv9iG+VQ0CDqa/472ZH4
         ZLiwI7i+15x7HonaloCcnWfV4FttDP/TPM3p2UsDz5v0VblAE5O9nZwab64RDNqV3opD
         7FsmVJfUTiNXRzlngH1jz6B/+5K6WkRxPX5/s=
MIME-Version: 1.0
In-Reply-To: <BANLkTikAbVYrqrFipxD2yVF5Nto405L0kw@mail.gmail.com>
References: <1305837612335-4410859.post@n5.nabble.com>
 <20110520051057.1B5623AD@athena.apache.org>
 <BANLkTikK8Fc1Uy7qdwtObLLEsXxjqv8Sjw@mail.gmail.com>
 <BANLkTimb0DVOALibXDzwZ-OexHOTFmOUjg@mail.gmail.com>
 <BANLkTikAbVYrqrFipxD2yVF5Nto405L0kw@mail.gmail.com>
From: Claus Ibsen <claus.ibsen@gmail.com>
Date: Sat, 21 May 2011 13:58:54 +0200
Message-ID: <BANLkTi=Gf5=URBjnKT+f=X-D7vihmnk=eA@mail.gmail.com>
Subject: Re: an un-easy way to use camel-xpath in:header() function
To: users@camel.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi

You can use a POJO to set the header using xpath.
The xpath builder was designed to work on the message body.

I wonder if your use case is widespread used, so its okay to alter the
code to support the use case?


On Fri, May 20, 2011 at 11:23 AM, tobeand <tobeand@gmail.com> wrote:
> I guess the XPath language of Camel has one limitation. That is the
> body of input message must be a valid XML or null.
>
> In this problem, user want use XPath to process a xml in message
> header, but the message body is a plain text (not valid XML), and an
> exception occurs in parsing the content to DOM.
>
> After reading source code, we found that the
> XPathBuilder.doInEvaluateAs() method try to extract the document from
> the input message, and pass the document to XPathExpression.evaluate()
> method. The XPathBuilder.getDocument() method creates an InputSource
> for the text body and then the XPathExpression.evaluate() method
> creates a DocumentBuilder to parse the InputSource.
>
>
>
> On Fri, May 20, 2011 at 2:24 PM, Taariq Levack <taariql@gmail.com> wrote:
>> Also if null or an empty xml is valid in some situations, then a content
>> based router in front of this should do niely.
>>
>> On Fri, May 20, 2011 at 8:18 AM, Taariq Levack <taariql@gmail.com> wrote=
:
>>
>>> Have you looked at the Validation component?
>>> http://camel.apache.org/validation.html
>>>
>>>
>>> On Fri, May 20, 2011 at 7:10 AM, ext2 <xuhb@tongtech.com> wrote:
>>>
>>>> Using camel's in:header() xpath function, =A0we can deal with =A0xml s=
tored in
>>>> message header very easy; for example:
>>>> =A0 =A0 =A0 =A0<setHeader name=3D"cheaperBooks">
>>>>
>>>> =A0<xpath>in:header('bookstore')/child::book[price<100]</xpath>
>>>> =A0 =A0 =A0 =A0</setHeader>
>>>>
>>>> The setHeader could retrieve all cheaper books(price less than 100) fr=
om a
>>>> bookstore xml (which already stored in message header('bookstore')
>>>>
>>>> But in camel, things are not always so easy. The user must make sure i=
nput
>>>> message's body must be a valid XML or null(although the body's content=
 may
>>>> have nothing to do with the bookstore xml). Otherwise the above xapth
>>>> express will failed;
>>>>
>>>> Suggestion(Maybe):
>>>>
>>>> Camel's XPath expression should check if the input body's content coul=
d be
>>>> convert to xml. If the body cannot, then using a null instead of origi=
nal
>>>> message body to do XPathExpression.evaluate;
>>>>
>>>>
>>>>
>>>
>>
>


--=20
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
CamelOne 2011: http://fusesource.com/camelone2011/
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/