Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: pass (athena.apache.org: domain of raul@evosent.com designates
 209.85.220.45 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <002201ce8d05$7f386bc0$7da94340$@de>
References: <001901ce8d02$c895baf0$59c130d0$@de>
 <CAGB5yN=2SwQSaAFgoCz7sp-SbsYDRU0oq60GAWb0CALmQ1ko=A@mail.gmail.com>
 <002201ce8d05$7f386bc0$7da94340$@de>
From: Raul Kripalani <raul@evosent.com>
Date: Tue, 30 Jul 2013 11:06:52 +0100
Message-ID: 
 <CAKoNANu3-O8XK-vOP123X91nxB5wjZEN3bJ7W5y0cGrRobdNKg@mail.gmail.com>
Subject: Re: XPath + DOM-reuse
To: "users@camel.apache.org" <users@camel.apache.org>
Content-Type: multipart/alternative; boundary=047d7b339c03fbbb9704e2b7c567

--047d7b339c03fbbb9704e2b7c567
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Just a little tip. Be careful with concurrency as DOM is not thread-safe.

So if you've got multiple XPath expressions or XSLT transformations running
in parallel (e.g. multicast EIP), you might get errors.

Regards,
Ra=FAl.

On Tue, Jul 30, 2013 at 10:16 AM, Jan Mat=E8rne (jhm) <apache@materne.de>wr=
ote:

> Thanks, I will try ...
>
> Jan
>
> > -----Urspr=FCngliche Nachricht-----
> > Von: Claus Ibsen [mailto:claus.ibsen@gmail.com]
> > Gesendet: Dienstag, 30. Juli 2013 11:09
> > An: users@camel.apache.org
> > Betreff: Re: XPath + DOM-reuse
> >
> > Hi
> >
> > You can convert the body to DOM first
> >
> > from
> > .convertBodyTo(Document.class)
> > choice
> >
> >
> >
> >
> > Also you can add camel-saxon to the classpath to use saxon as the xpath
> > engine. Its faster than what comes out of the box in the JDK.
> >
> >
> > You can use vtd-xml for an xpath language that can work with streamed
> > data types http://camel.apache.org/vtd-xml
> >
> > On Tue, Jul 30, 2013 at 10:57 AM, Jan Mat=E8rne (jhm) <apache@materne.d=
e>
> > wrote:
> > > I have a route dispatching an exchange according to a XPath
> > evaluation
> > > to different targets.
> > >
> > > Sadly it doesnt perform very well. I think that the DOM is built for
> > > every XPath evalutation.
> > >
> > > Is it true? Can we configure Camel to reuse the DOM?
> > >
> > >
> > >
> > > I think in this Route Camel builds the same DOM 4 times.
> > >
> > >
> > >
> > > public class MyRouter extends RouteBuilder {
> > >
> > >     @Override
> > >
> > >     public void configure() throws Exception {
> > >
> > >         Namespaces v1 =3D new Namespaces("v1", "...");
> > >
> > >         Namespaces v2 =3D new Namespaces("v2", "...");
> > >
> > >
> > >
> > >         from("direct:dispatcher")
> > >
> > >             .id("dispatcher")
> > >
> > >             .choice()
> > >
> > >                 .when().xpath("/v1:TypeA",
> > > v1).to("bean:beanA?method=3Dexecute")
> > >
> > >                 .when().xpath("/v1:TypeB",
> > > v1).to("bean:beanB?method=3Dexecute")
> > >
> > >                 .when().xpath("/v2:TypeA",
> > > v2).to("bean:beanC?method=3Dexecute")
> > >
> > >                 .when().xpath("/v2:TypeB",
> > > v2).to("bean:beanD?method=3Dexecute")
> > >
> > >                 // many more when().xpath().to() statements
> > >
> > >             .end();
> > >
> > >     }
> > >
> > > }
> > >
> > >
> > >
> > >
> > >
> > > Jan
> > >
> >
> >
> >
> > --
> > Claus Ibsen
> > -----------------
> > Red Hat, Inc.
> > Email: cibsen@redhat.com
> > Twitter: davsclaus
> > Blog: http://davsclaus.com
> > Author of Camel in Action: http://www.manning.com/ibsen
>
>

--047d7b339c03fbbb9704e2b7c567--