[
https://issues.apache.org/jira/browse/AMQ-2018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved AMQ-2018.
------------------------------
Resolution: Later
Assignee: Claus Ibsen
AMQ runs fine with spring-dm 1.2.
> ActiveMQ not deployable in spec-compliant OSGi container
> --------------------------------------------------------
>
> Key: AMQ-2018
> URL: https://issues.apache.org/jira/browse/AMQ-2018
> Project: ActiveMQ
> Issue Type: Improvement
> Affects Versions: 5.2.0
> Environment: SpringSource dm Server 1.0
> Reporter: Jon Brisbin
> Assignee: Claus Ibsen
> Priority: Minor
> Fix For: NEEDS_REVIEWED
>
>
> The SpringSource dm Server manifest parser is strictly OSGi spec-compliant
> and fails to deploy ActiveMQ jar files because the default manifest
> references a package name starting with META-INF. The xbean schema property
> files aren't even usable in dm server anyway, so there's no reason to include
> META-INF in the classpath. The OSGi spec prohibits this apparently.
> I've created an issue with SpringSource to have ActiveMQ 5.2 added to their
> bundle repository, but it would better if the standard AMQ jars were
> distributable as bundles in dm Server as easily as they are in a runtime like
> Apache Felix. This would just require patching the build to not include
> META-INF in either export or import package.
--
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
