[SWS-417] spring-ws-core-tiger should be declared as an OSGi fragment since it contributes classes to packages from spring-ws-core Created: 20/Aug/08 Updated: 04/May/12 Resolved: 22/Sep/08
|Project:||Spring Web Services|
|Reporter:||Michael Pilquist||Assignee:||Arjen Poutsma|
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
Currently, despite all Spring WS JARs being OSGi bundles, you can't use classes from spring-ws-core-tiger in an OSGi container. This is due to spring-ws-core-tiger exporting packages that are already exported by spring-ws-core.
The easiest fix for this would be to change spring-ws-core-tiger to a fragment bundle, with its host bundle set to spring-ws-core. This can be fixed by adding the following manifest entry to spring-ws-core-tiger.
Fragment-Host: org.springframework.bundle.ws.core;version="[1.5.4, 1.5.4]"
I have not checked if the oxm/oxm-tiger JARs have a similar issue.
|Comment by Arjen Poutsma [ 21/Sep/08 ]|
As a temporary workaround, you can use the Bundle Repository bundles, for instance:
|Comment by Arjen Poutsma [ 04/May/12 ]|
Closing old issues