Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Received-SPF: pass (nike.apache.org: domain of claus.ibsen@gmail.com
 designates 209.85.223.172 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <F3B95D9661E15E459E329DCDC7529AA4B8ADE5A5@DEWDFEMB17A.global.corp.sap>
References: 
 <F3B95D9661E15E459E329DCDC7529AA4B8ADE5A5@DEWDFEMB17A.global.corp.sap>
From: Claus Ibsen <claus.ibsen@gmail.com>
Date: Sat, 17 Jan 2015 11:34:12 +0100
Message-ID: 
 <CAGB5yNksu1FH3Ci2p7y313ARxnkWtbGy=OUiEL0zVvFOyaRL2g@mail.gmail.com>
Subject: Re: Question about documentType in XPathBuilder
To: dev <dev@camel.apache.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Ad 2)
I think there is already a JIRA about that. Its not so hard to do,
look in the model.language packages of camel-core, and add a
getter/setter and jaxb annotation for it to be in the xsd. And add the
logic to configure it as well, like the other options.

https://issues.apache.org/jira/browse/CAMEL-8182

On Fri, Jan 16, 2015 at 1:52 PM, Siano, Stephan <stephan.siano@sap.com> wro=
te:
> Hi,
>
> If you look into the XPathBuilder in camel (actually the doInEvaluateAs()=
 method), you see that the data that the evaluated with the XPath expressio=
n (a header or the body) is first converted into a data type defined in the=
 documentType attribute of the XPath builder. Afterwards the expression is =
evaluated with the Object (or the node attribute of it if it is a DOMSource=
).
>
> The default for the documentType is Document (DOM), which is pretty much =
memory consuming. On large XML documents (e.g. 100 MB) parsing a DOM may le=
ad to an OutOfMemoryError. If the Saxon parser is used for transformation, =
the implementation is capable of using a TinyTree instead of e Xerces DOM, =
which is much smaller, however that doesn't help if the JVM goes OOM when p=
arsing the Document with the Xerces parser into a DOM tree even before the =
transformation takes place.
>
> In Java DSL it is possible to set the documentType to an XPath expression=
 (as in)
>         from("direct:setbody")
>             .setBody(xpath("/a/b/c", Document.class)
>                     .documentType(SAXSource.class)
>                     .factory(new XPathFactoryImpl())
>                     );
>
> The route is capable of transforming much larger Documents than the same =
route without the .documentType(SAXSource.class) statement (InputSource wil=
l also work if the incoming data has a type converter to InputSource).
>
> In XML DSL there is unfortunately no way to set the document type.
>
> I have some questions about that:
>
> 1.       Does anybody know why Document was taken as a default documentTy=
pe?
>
> 2.       Why is the documentType not configurable in XML DSL? What would =
I need to do in order to add an extra attribute to the XML DSL?
>
> 3.       Wouldn't a more dynamic approach be better? E.g. if the  data is=
 a DOM tree from the beginning us that, if it's a SAXSource use that one an=
d if it's something like an InputStream or String use an InputSource?
>
> What do you think about this?
>
> Best regards
> Stephan


--=20
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
hawtio: http://hawt.io/
fabric8: http://fabric8.io/