It seems that we can use the NettyRequestTimeoutIussueTest to reproduer
this issue. But it needs to be run manually and I have checked it with the
master branch and there is a failure in the camel-netty-test.log
I sent the PR [2] with my proposal to fix this issue.
[1]
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
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
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
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
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
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
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
Hello,
I have a Jhipster UAA Server based Spring Boot(2.1.9 RELEASE) application which
loads PKCS12 file in UAAServer. Once I added Camel 3 Dependency the KeyStore
API's started giving errors.
Hi Cameleers,
we have a discussion on pull request #397[1] about merging the
Documentation and Projects sections on the website. This came about
from a fair bit of duplication we currently have between those two
pages and we're trying to consolidate and simplify.
We're looking for community
No, it's not wrong. The Keystore works with the same password if I remove Camel
dependency. With camel added, it gives the error. Some more Information from
Java Security Logs. Not sure why in non-working logs code picks bouncycastle.
Non-working logs:
Provider: KeyStore.JKS type from: SUN
The error is explicit.
Il mer 17 giu 2020, 21:47 Mrinal Sharma ha scritto:
> Hello,
>
> I have a Jhipster UAA Server based Spring Boot(2.1.9 RELEASE) application
> which loads PKCS12 file in UAAServer. Once I added Camel 3 Dependency the
> KeyStore API's started giving errors.
>
>
The keystore password is wrong.
Il mer 17 giu 2020, 22:33 Mrinal Sharma ha scritto:
> Can you elaborate more?
>
> -Original Message-
> From: Andrea Cosentino
> Sent: Wednesday, June 17, 2020 3:54 PM
> To: users@camel.apache.org
> Subject: Re: Apache Camel Issue with Spring Boot 2.1.9
Can you elaborate more?
-Original Message-
From: Andrea Cosentino
Sent: Wednesday, June 17, 2020 3:54 PM
To: users@camel.apache.org
Subject: Re: Apache Camel Issue with Spring Boot 2.1.9 RELEASE
CAUTION - EXTERNAL EMAIL This email originated from outside of Smith Micro
Software. Do
14 matches
Mail list logo
