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 2008/11/05 05:29:05 UTC
[jira] Assigned: (SMX4KNL-134) XPathFactoryFinder in jaxp api
should use factoryId to load the spi class in osgi enviroment
[ https://issues.apache.org/activemq/browse/SMX4KNL-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Freeman Fang reassigned SMX4KNL-134:
------------------------------------
Assignee: Freeman Fang
> XPathFactoryFinder in jaxp api should use factoryId to load the spi class in osgi enviroment
> --------------------------------------------------------------------------------------------
>
> Key: SMX4KNL-134
> URL: https://issues.apache.org/activemq/browse/SMX4KNL-134
> Project: ServiceMix Kernel
> Issue Type: Bug
> Reporter: Freeman Fang
> Assignee: Freeman Fang
> Fix For: 1.1.0
>
>
> currently it use
> Class spiClass = org.apache.servicemix.specs.locator.OsgiLocator.locate(propertyName); // the property name here is javax.xml.xpath.XPathFactory+uri
> but in osgi container we register the service with key javax.xml.xpath.XPathFactory, something like
> registering service for key javax.xml.xpath.XPathFactorywith value bundle://4.0:0/META-INF/services/javax.xml.xpath.XPathFactory
> so we need use javax.xml.xpath.XPathFactory as the key for org.apache.servicemix.specs.locator.OsgiLocator to find the spiClass
> both jaxp 1.3 and jaxp 1.4 api need this fix
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.