Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (nike.apache.org: domain of jim.robinson@gmail.com
 designates 209.85.220.41 as permitted sender)
MIME-Version: 1.0
Sender: jim.robinson@gmail.com
In-Reply-To: <1426700946241-4693426.post@n4.nabble.com>
References: <1426527939611-4693314.post@n4.nabble.com>
 <1426686071476-4693409.post@n4.nabble.com>
 <CAPd04b6+nuU3ZAyLaKEH1X+SrObpODDfDaQ58Z1Md-QV1hBLnw@mail.gmail.com>
 <1426691849836-4693415.post@n4.nabble.com>
 <CAPd04b6Esd_gZajVGV+1TjDVi7=v3gwr37PoSZnH8WpkpDA9Lw@mail.gmail.com>
 <1426700946241-4693426.post@n4.nabble.com>
From: "James A. Robinson" <jimr@highwire.org>
Date: Wed, 18 Mar 2015 13:35:53 -0700
Message-ID: 
 <CAPd04b7+untyD67sLNMTyCz8UqVdCy22=iEDak-qywDdWZUYzw@mail.gmail.com>
Subject: Re: ActiveMQ 5.11 Dynamic Camel Route - Message Namespaces
To: users@activemq.apache.org
Content-Type: text/plain; charset=UTF-8

On Wed, Mar 18, 2015 at 10:49 AM, mtod <mtod@thetods.net> wrote:
>  INFO | Created default XPathFactory
> com.sun.org.apache.xpath.internal.jaxp.XPathFactoryImpl@343985bd
>  INFO | Creating new XPath expression in pool. Namespaces on XPath
> expression: [me: {system ->
> http://camel.apache.org/xml/variables/system-properties},{env ->
> http://camel.apache.org/xml/variables/environment-variables},{in ->
> http://camel.apache.org/xml/in/},{function ->
> http://camel.apache.org/xml/function/},{out ->
> http://camel.apache.org/xml/out/}]
>  INFO | Namespaces discovered in message:
> {xmlns:km=[http://xsdrepo.foundationmedicine.com/messaging/esb],
> xmlns:xsi=[http://www.w3.org/2001/XMLSchema-instance],
> xmlns:bm=[http://xsdrepo-dev.foundationmedicine.com/messaging/esbbamevent]}.

Taking a look at this:

http://camel.apache.org/maven/current/camel-core/apidocs/src-html/org/apache/camel/builder/xml/XPathBuilder.html

the order of operations appears to be

protected Object evaluateAs(Exchange exchange, QName resultQName) {
...
xpathExpression = createXPathExpression();
...
logNamespaces(exchange);
...
}

where createXPathExpression() logs:

LOG.trace("Creating new XPath expression in pool. Namespaces on XPath
expression: {}", getNamespaceContext().toString());

before calling:

xPath.setNamespaceContext(getNamespaceContext());

and that getNamespaceContext() result does not appear to contain your namespace.

whereas logNamespaces(Exchange exchange) builds one of:

answer = (NodeList) xpathExpression.evaluate(inputSource,
XPathConstants.NODESET);
answer = (NodeList) xpathExpression.evaluate(source.getNode(),
XPathConstants.NODESET);
answer = (NodeList) xpathExpression.evaluate(document, XPathConstants.NODESET);

based on the input type and then calls

logDiscoveredNamespaces(answer)

which iterates over answer and apparently *does* contain your namespace.

I would suspect this is a bug in what getNamespaceContext() is returning...


Jim