Its with the other spring xmlns declarations
http://www.springframework.org/schema/beans";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
*xmlns:x="urn:iso:std:iso:20022:tech:xsd:DRAFT15auth.016.001.01"*
xmlns:camel="http://camel.apache.org/schema/spring";
Nice.
Did you change the XML and added the namespace prefix or did you handle it in
code?
M
> On 18 Jun 2020, at 15:15, bob anderson wrote:
>
> Hi ,
>
> I know you are using JAVA DSL, but I have got what you want using the XML
> DSL, maybe someone can put you right from my example.
>
> The
Hi ,
I know you are using JAVA DSL, but I have got what you want using the XML
DSL, maybe someone can put you right from my example.
The two points that are probably important are
1) Giving the namespace a prefix -
xmlns:x="urn:iso:std:iso:20022:tech:xsd:DRAFT15auth.016.001.01"
2) In the seco
Hi!
I have read that since camel 3 you are dropping support for multiple camel
contexts within the same process.
Is there a plan to implement an alternative way to namespace routes and
endpoints, to avoid name conflicts?
Thanks,
Ciprian
My latest tests reveal that when using local-name() I get everything with the
tag (of course).
But I cannot see how to manipulate the xpath expression.
final XPathBuilder xPathBuilder = XPathBuilder.xpath("//*[local-name()='Tx']");
When trying out it in http://xpather.com/ using
//FinInstrmR
Hi,
I followed camel-example-micrometer (v2.22.2) and see only jvm metrics
under localhost:8088/metrics
and no metrics from the route direct:bar below. How to make these
available in /metrics output as well?
from("netty4-http:http://0.0.0.0:8088/metrics";)
.routeId("netty
The Camel community announces the immediate availability of Camel,
Camel Spring Boot and Camel Karaf 3.4.0, a new LTS release with 118
new features, improvements and fixes.
The artifacts are published and ready for you to download [1] either
from the Apache mirrors or from the Central Maven reposi
Found the local namespace trick working but not as I expected. It found the
inner Tx instead.
Back to square on.
Thx for all input so far
// Mikael Andersson Wigander
> 18 juni 2020 kl. 10:39 skrev Claus Ibsen :
>
> On Thu, Jun 18, 2020 at 10:15 AM Mikael Andersson Wigander
> wrote:
>>
>
Hi, I think that two links should be immediately visible in the
homepage/menu: documentation and download. For this reason I prefer
documentation. I like the fact that we are highlighting the base Camel
framework in the preview, but there is no example link like in the
other projects and I would in
On Thu, Jun 18, 2020 at 10:15 AM Mikael Andersson Wigander
wrote:
>
> OK, interesting.
>
> I tested the Xpath using a online tester and there it works without using any
> namespace.
>
> Is it possible using XPath without namespaces or are there any xpath
> arguments that can be used?
>
No reall
Indeed, I think documentation serves what I would expect from that page.
Regards,
Omar
On Thu, Jun 18, 2020 at 8:59 AM Ajmera, Hemang C
wrote:
> Hi
>Earlier in UI the mouse over on menu would should be direct link for
> Components documents Now mouse over is not working. May be we can
>
OK, interesting.
I tested the Xpath using a online tester and there it works without using any
namespace.
Is it possible using XPath without namespaces or are there any xpath arguments
that can be used?
M
> On 18 Jun 2020, at 09:53, Alex Dettinger wrote:
>
> Hi Mikael,
>
> I've noticed th
Hi Mikael,
I've noticed that the incoming xml file is involving 2 xml namespaces
while the query looks not.
Precising namespaces in the xpath query may help to move further, something
like:
https://github.com/apache/camel/blob/master/core/camel-core/src/test/java/org/apache/camel/builder/xml/XPa
Hi
My problem is that I can’t extract some XML using xpath in Camel 3.3.0
My incoming XML is complicated where my target tag also has a tag
further down the tree as .
I have created a demo project on Github for share if someone could help me.
https://github.com/hakuseki/xpath
I have tested w
14 matches
Mail list logo
