> I haven't taken it for spin yet, but
> it's worth a try.
Also James added VTD XML component to Camel Extra, if extra-fast XPath
query is fair enough for you.
[1] http://camel.apache.org/vtd-xml
--
Henryk Konsek
http://henryk-konsek.blogspot.com
compario.in refers to a jaxb.index file
> > which refers to a java class named ResponseCompario.java
> >
> > It works fine but i was wondering, is this route more performant ?:
> > from("endpointIn")
> > .convertBodyTo(ResponseCompario.class)//
> > .process(.
> Avoid usage of DOM or big object trees.
Good point. I assumed that the entire XML needs to be parsed (this is
often the case). But yeah, definitely favor streaming over
deserializing entire XML.
--
Henryk Konsek
http://henryk-konsek.blogspot.com
ompario.java
>
> It works fine but i was wondering, is this route more performant ?:
> from("endpointIn")
> .convertBodyTo(ResponseCompario.class)//
> .process(...)
>
> NB: The xml files are pretty big.
>
> Best regards,
>
>
>
> --
> View
route more performant ?:
> from("endpointIn")
> .convertBodyTo(ResponseCompario.class)//
> .process(...)
>
> NB: The xml files are pretty big.
>
> Best regards,
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Parsing-XML-Performance-tp5727867.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
--
Hi,
> It works fine but i was wondering, is this route more performant ?:
> NB: The xml files are pretty big.
If XML (de)serialization is an issue consider using JiBX data format [1].
from("direct:start").unmarshal().jibx(MyMappedBean.class).to(...);
JiBX is a speed demon comparing to JAXB.
Be
-
View this message in context:
http://camel.465427.n5.nabble.com/Parsing-XML-Performance-tp5727867.html
Sent from the Camel - Users mailing list archive at Nabble.com.
