Mailing-List: contact camel-user-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: camel-user@activemq.apache.org
Received-SPF: pass (athena.apache.org: domain of james.strachan@gmail.com
 designates 66.249.82.227 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=opsY6ZYpLfpScDWxjfO1NUPt+gJs7QqhKcj5bKmsPKhszTj6VEAe0wJnoBdnSFSlVBFC28Cet0MR8GXGj9DsbeM/maUGVivhjeZtufo7o1f7JNwor0UZIHX4fILJq+88x+V/krSh3EGMixlMpdCeu2rL4jpc5GivCj6xxH48PUE=
Message-ID: <ec6e67fd0710310922s4513d198y370546f8264a67ff@mail.gmail.com>
Date: Wed, 31 Oct 2007 16:22:48 +0000
From: "James Strachan" <james.strachan@gmail.com>
To: camel-user@activemq.apache.org
Subject: Re: How to enrich message with the result of other invocation
In-Reply-To: <ec6e67fd0710300940w1cb39c7dwf95ace4f5eb0c705@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <f1c427510710291237m352497b8r1b26fd45f9647ef0@mail.gmail.com>
	 <ec6e67fd0710300940w1cb39c7dwf95ace4f5eb0c705@mail.gmail.com>

On 30/10/2007, James Strachan <james.strachan@gmail.com> wrote:
> On 29/10/2007, Roman Kalukiewicz <roman.kalukiewicz@gmail.com> wrote:
> > Hello!
> >
> > I'm looking for elegant solution for following problem:
> >
> > I receive request that is an XML document or object. I need to enrich
> > it (add new element or set a property). The problem is that the value
> > I want to enrich with is the result of some endpoint invocation.
> >
> > I know that I can do it using custom processor, but maybe there is
> > some Expression instance that evaluates to result of endpoint
> > invocation? this way I can simply use setBody() or setHeader() methods
> > with such Expression.
> >
> > Or maybe there is better way to do it? I'm just curious if I can avoid
> > using custom processors and express everything in DSL.
>
> Interesting use case! :) Am sure over time we'll figure out nicer and
> richer ways of putting all kinds of things like this into the DSL.
>
> I wonder if we could expose 'invoke an endpoint' nicely inside XSLT or
> XQuery to make it easy to enrich messages that way?
>
> Am sure we could do something like
>
> let $doc := .
> for $invoke in camel-invoke("some-uri")/*
> return <result>{ $doc, $invoke }</result >
>
> I couldn't see an easy way to use XQuery to say effectively, 'add the
> XQuery expression into the context node as a child' - am sure with
> more XQuery ninja there's a way to do it a bit cleaner.

A maybe cleaner way to do it in XQuery is something like this...

<result>
{/*}
{camel-invoke('some-uri')}
</result>

This will embed the original document inside <result> then the result
of the camel-invoke method in there too.

I've not seen a cleaner way to put the invocation inside the first
child of the input yet though.

-- 
James
-------
http://macstrac.blogspot.com/

Open Source SOA
http://open.iona.com