You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Babak Vahdat (JIRA)" <ji...@apache.org> on 2012/09/12 11:27:10 UTC

[jira] [Comment Edited] (SMX4-1240) OSGi bundle for Saxon 9.4.0.4

    [ https://issues.apache.org/jira/browse/SMX4-1240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13453851#comment-13453851 ] 

Babak Vahdat edited comment on SMX4-1240 at 9/12/12 8:25 PM:
-------------------------------------------------------------

No that information isn't inside MANIFEST.MF, but inside files beneath the META-INF/services folder.

So *the root cause* of the problem is the following missing files inside the SMX bundle, which are already shipped with the one on the central Repo:

{code}
META-INF/services/javax.xml.xpath.XPathFactory
META-INF/services/javax.xml.transform.TransformerFactory
{code}

As an example the first file contains the class name of XPathFactory-Impl to be used (which is net.sf.saxon.xpath.XPathFactoryImpl). This's also exactly the same way how Camel itself detectes it's own component "foo" under the path "META-INF/services/org/apache/camel/component/foo" :-)
So when you try to make use of the SMX bundle on the classpath, then of course JDK defaults to it's own Impl, e.g. on SUN-JDK that would be:

{code}
com.sun.org.apache.xpath.internal.jaxp.XPathFactoryImpl
{code}

                
      was (Author: bvahdat):
    No that information isn't inside MANIFEST.MF, but inside files beneath the META-INF/services folder.

So *the root cause* of the problem is the following missing files inside the SMX bundle, which are already shipped with the one on the central Repo:

{code}
META-INF/services/javax.xml.xpath.XPathFactory
META-INF/services/javax.xml.transform.TransformerFactory
{code}

As an example the first file contains the class name of XPath-Impl to be used (which is net.sf.saxon.xpath.XPathFactoryImpl). This's also exactly the same way how Camel itself detectes it's own component "foo" under the path "META-INF/services/org/apache/camel/component/foo" :-)
So when you try to make use of the SMX bundle on the classpath, then of course JDK defaults to it's own Impl, e.g. on SUN-JDK that would be:

{code}
com.sun.org.apache.xpath.internal.jaxp.XPathImpl
{code}

                  
> OSGi bundle for Saxon 9.4.0.4
> -----------------------------
>
>                 Key: SMX4-1240
>                 URL: https://issues.apache.org/jira/browse/SMX4-1240
>             Project: ServiceMix 4
>          Issue Type: Task
>          Components: Bundles
>            Reporter: Claus Ibsen
>            Assignee: Jean-Baptiste Onofré
>            Priority: Minor
>
> http://repo2.maven.org/maven2/org/apache/servicemix/bundles/org.apache.servicemix.bundles.saxon/
> http://www.saxonica.com/welcome/welcome.xml
> 25 June 2012  Saxon 9.4.0.4 is available (Saxon-HE...)
> We got 9.4.0.1 currently as osgi bundle. But there is a newer release out.

--
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