Well now my original problem has turned to a split/xpath problem.
Trying to split on either the tag as Tx or using //Tx or using
//FinInstrmRptgTxRpt/Tx returns nothing.
Tried online xpath parsers and they return the correct xml for the last two (as
mentioned above).
Tried 2.25.1 and 3.3.0
Hi
Yeah there is the problem with some xml libraries not working in
streaming mode where they can process the data in chunks, so they have
to load all content into memory.
The tokenizer from Camel does not have that problem, but it can have
others like not being able to match the right ending tag.
HI
Some time back (couple of years) I used split xtokenize on a large XML
file at three levels which has worked very well. Two of the three elements
had the same tags, however I needed elements from each level so did the
split tokenize in separate routes i.e. split/tokenize (get an element) call
Hi
It can be both, hower its a little better as an argument
split(xpath(), )
On Wed, Jun 17, 2020 at 1:10 PM Mikael Andersson Wigander
wrote:
>
> Hi
>
> Makes sense.
>
> Tried splitting using xpath but it didn’t work either.
> Should xpath be as argument of split or own statement (.xp
Hi
Makes sense.
Tried splitting using xpath but it didn’t work either.
Should xpath be as argument of split or own statement (.xpath())?
// Mikael Andersson Wigander
> 17 juni 2020 kl. 10:14 skrev Claus Ibsen :
>
> Hi
>
> No tokenizeXml is for not complex XML with tags that are nested. It
Hi
No tokenizeXml is for not complex XML with tags that are nested. It
uses regexp parsing etc.
Instead using camel-stax or camel-jaxb or something like that.
On Wed, Jun 17, 2020 at 9:14 AM Mikael Andersson Wigander
wrote:
>
> Hi
>
> We have a XML file to split on tag .
> However this tag is
Hi
We have a XML file to split on tag .
However this tag is also present in a node further down the tree as well.
tokenizeXML is used in our application but now this won’t work because it ends
prematurely.
Here’s the XML
1312312
