You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Freeman Fang (JIRA)" <ji...@apache.org> on 2013/03/13 03:20:14 UTC
[jira] [Commented] (SMX4-1375) Unable to use Saxon implementation
for camel xpath
[ https://issues.apache.org/jira/browse/SMX4-1375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13600731#comment-13600731 ]
Freeman Fang commented on SMX4-1375:
------------------------------------
@David
I noticed that currently servicemix-saxon feature still use
org.apache.servicemix.bundles.saxon 9.3.x
That version is old and buggy, especially has not entry like
{code}
META-INF/services/javax.xml.transform.TransformerFactory
META-INF/services/javax.xml.xpath.XPathFactory
{code}
in the bundle, which may cause the issue you encounter.
Could you please try with the latest org.apache.servicemix.bundles/org.apache.servicemix.bundles.saxon/9.4.0.4_2
instead to see if it helps?
You can edit
$SMX4_HOME/system/org/apache/servicemix/apache-servicemix/4.5.0/apache-servicemix-4.5.0-features.xml
change org.apache.servicemix.bundles.saxon version to 9.4.0.4_2 in servicemix-saxon feature, then remove $SMX4_HOME/data folder and restart Servicemix
Freeman
> Unable to use Saxon implementation for camel xpath
> --------------------------------------------------
>
> Key: SMX4-1375
> URL: https://issues.apache.org/jira/browse/SMX4-1375
> Project: ServiceMix 4
> Issue Type: Bug
> Components: Bundles
> Affects Versions: 4.5.0
> Environment: Windows 7
> Reporter: David Daum
> Fix For: 4.5.1
>
>
> features:install servicemix-saxon ...yields error...
> Error executing command: URL [mvn:org.apache.servicemix.naming/org.apache.servicemix.naming/1.6.0] could not be resolved.
> ------------------------
> when using <xpath saxon="true" in camel route, the following error is seen:
> No XPathFctory implementation found for the object model: http://saxon.sf.net/jaxp/xpath/om
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira