[
https://issues.apache.org/jira/browse/SM-4762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17361015#comment-17361015
]
Veselin commented on SM-4762:
-----------------------------
Well I've found another solution for my product:
|jakarta.xml.bind:jakarta.xml.bind-api|2.3.3|Jakarta persistence api|
|com.sun.xml.bind:jaxb-osgi|2.3.4|Seperated jaxb implementation|
|org.glassfish.hk2:osgi-resource-locator|1.0.1|Resource locator to make jaxb
factory available in osgi context|
I've added the bundles above and just that is enough for me to have JAX-B 2.3.
I guess you can close the ticket.
> JAXB API 2.3 imports javax.xml.stream 1.0
> -----------------------------------------
>
> Key: SM-4762
> URL: https://issues.apache.org/jira/browse/SM-4762
> Project: ServiceMix
> Issue Type: Bug
> Components: specs
> Affects Versions: jaxb-api-2.3_1
> Reporter: Veselin
> Assignee: Freeman Yue Fang
> Priority: Major
>
> The bundle org.apache.servicemix.specs.jaxb-api-2.3 is importing the package
> javax.xml.stream in version 1.0. This prevents it to load the package from
> JavaSE and forces me to install other bundles exporting the package.
> I'm just trying to upgrade my JAXB implementation to version 2.3.
> My goal is to add the following bundles to my felix container and be done
> with it:
> org.apache.servicemix.specs.jaxb-api-2.3-2.3_3.jar
> org.apache.servicemix.bundles.jaxb-runtime-2.3.2_2.jar
> javax.activation-api-1.2.0.jar
> javax.activation-1.2.0.jar
> osgi-resource-locator-1.0.1.jar
>
> Is it really required for the bundle to import javax.xml.stream v1.0?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
