You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2011/05/29 15:49:47 UTC

[jira] [Resolved] (CAMEL-4025) XPath namespaces not present when element inside a element

     [ https://issues.apache.org/jira/browse/CAMEL-4025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen resolved CAMEL-4025.
--------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 2.9.0)
                   2.8.0

> XPath namespaces not present when <xpath> element inside a <routeContext> element
> ---------------------------------------------------------------------------------
>
>                 Key: CAMEL-4025
>                 URL: https://issues.apache.org/jira/browse/CAMEL-4025
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-spring
>    Affects Versions: 2.6.0, 2.7.1
>         Environment: OSX 10.6.7
> java version "1.6.0_24"
> Java(TM) SE Runtime Environment (build 1.6.0_24-b07-334-10M3326)
> Java HotSpot(TM) 64-Bit Server VM (build 19.1-b02-334, mixed mode)
>            Reporter: Paul Mietz Egli
>            Assignee: Claus Ibsen
>             Fix For: 2.8.0
>
>         Attachments: SpringXPathFilterWithNamespaceOnRouteContextTest.java, xpathFilterWithNamespaceOnRouteContext.xml
>
>
> I have a route that is inside a {{<routeContext>}} element which uses XPath as part of a filter and a choice.  The input document has a default namespace that is not blank.  When I try to run a message through the route, I see the following error in the logs:
> {code:none}
> com.sun.org.apache.xpath.internal.domapi.XPathStylesheetDOM3Exception: Prefix must resolve to a namespace: foo
> {code}
> Adding the namespace declaration to the {{beans}} element as is done in the unit tests for camel-spring doesn't fix the problem, and neither does adding it to the {{<camelContext>}} element as described in the documentation.  I copied the {{SpringXPathFilterWithNamespaceTest}} class and created an input route configuration that uses a {{routeContext}}, and was able to reproduce the issue.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira