[
https://issues.apache.org/jira/browse/SM-3020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Martin updated SM-3020:
-------------------------------------
Description:
cf.
http://servicemix.396122.n5.nabble.com/NoClassDefFoundError-using-Xerces-XmlResolver-td5723624.html
In a nutshell, Xerces bundle wants to use a class
(org/apache/xml/resolver/CatalogManager) contained in XmlResolver bundle but
can't reach it (due to classloading mechanism).
The issue can be resolved if XmlResolver's classes are loaded by the same
classloader as Xerces's one (the bootstrap / primordial classloader). In our
case, this consists in :
- Adding XmlResolver jar file in <SMX_HOME>/lib/endorsed/
- Exporting 'org.apache.xml.resolver' to the bootdelegation packages (via
<SMX_HOME>/etc/config.properties file)
Should this solution be the default configuration ?
was:
cf.
http://servicemix.396122.n5.nabble.com/NoClassDefFoundError-using-Xerces-XmlResolver-td5723624.html
In a nutshell, Xerces wants to use a class
(org/apache/xml/resolver/CatalogManager) contained in XmlResolver but can't
reach it (due to classloading mechanism).
The issue can be resolved if XmlResolver's classes are loaded by the same
classloader as Xerces's one (the bootstrap / primordial classloader). In our
case, this consists in :
- Adding XmlResolver jar file in <SMX_HOME>/lib/endorsed/
- Exporting 'org.apache.xml.resolver' to the bootdelegation packages (via
<SMX_HOME>/etc/config.properties file)
Should this solution be the default configuration ?
> NoClassDefFoundError using Xerces / XmlResolver
> -----------------------------------------------
>
> Key: SM-3020
> URL: https://issues.apache.org/jira/browse/SM-3020
> Project: ServiceMix
> Issue Type: Bug
> Components: bundles
> Affects Versions: 6.1.0
> Reporter: Jean-Baptiste Martin
>
> cf.
> http://servicemix.396122.n5.nabble.com/NoClassDefFoundError-using-Xerces-XmlResolver-td5723624.html
> In a nutshell, Xerces bundle wants to use a class
> (org/apache/xml/resolver/CatalogManager) contained in XmlResolver bundle but
> can't reach it (due to classloading mechanism).
> The issue can be resolved if XmlResolver's classes are loaded by the same
> classloader as Xerces's one (the bootstrap / primordial classloader). In our
> case, this consists in :
> - Adding XmlResolver jar file in <SMX_HOME>/lib/endorsed/
> - Exporting 'org.apache.xml.resolver' to the bootdelegation packages
> (via <SMX_HOME>/etc/config.properties file)
> Should this solution be the default configuration ?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
