[
https://issues.apache.org/activemq/browse/SMX4-257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gert Vanthienen updated SMX4-257:
---------------------------------
Attachment: SMX4-257.diff
Attaching a patch for both bundles. The only thing I changed in Greg's fix was
append a _1 to the version number, everything else is just as it was. Not sure
why you need the split-package for the xalan packages...
Upon installation in ServiceMix Kernel, I now get a
org.osgi.framework.BundleException: Unresolved constraint in bundle 168:
package; (package=org.apache.xerces.parsers), so it looks like it needs Xerces
as well.
Greg, do you fancy taking another stab at adding that one as well?
> Provide a Xalan 2.7.1 bundle
> ----------------------------
>
> Key: SMX4-257
> URL: https://issues.apache.org/activemq/browse/SMX4-257
> Project: ServiceMix 4
> Issue Type: Task
> Reporter: Greg Lucas
> Assignee: Gert Vanthienen
> Attachments: SMX4-257.diff, xalan-2.7.1.zip,
> xalan-serializer-2.7.1.zip
>
>
> There is no Xalan 2.7.1 OSGi bundle available.
> The FuseSource maven repo has a bundled version of Xml-Security 1.4.2:
> http://repo.open.iona.com/maven2-all/org/apache/servicemix/bundles/org.apache.servicemix.bundles.xmlsec/1.4.2_1-fuse/
>
> If you try to load this bundle it complains that the XML-Security 1.4.2
> bundle can't be loaded due to org.apache.xml.dtm not being loaded. This
> package is in the Xalan 2.7.1 jar, but no bundle is available. Therefore to
> use the XML-Security 1.4.2 bundle in an osgi container, a Xalan 2.7.1 bundle
> is also needed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
