[
https://issues.apache.org/jira/browse/CXF-7910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16742748#comment-16742748
]
Freeman Fang commented on CXF-7910:
-----------------------------------
OK, I figured out why.
The jakarta soap-api 1.4 can't find saaj-impl bundle in OSGi container.
I'd say the SPI mechanism in OSGi is one of the most tricky part when running
CXF in OSGi container. And that's why we use Servicemix wrapped specs
bundles.There is definitely more work to use jaxws 2.3 and hence saaj-api
1.4(And some work need to be done at both Karaf and Servicemix side).
I suggest we postpone this issue to CXF 3.3.1, as I don't think we want to
delay CXF 3.3.0 release indefinitely.
What do you think guys?
Thanks!
Freeman
> Change JAX-WS javax to jakarta artifact dependencies
> ----------------------------------------------------
>
> Key: CXF-7910
> URL: https://issues.apache.org/jira/browse/CXF-7910
> Project: CXF
> Issue Type: Task
> Components: JAX-WS Runtime
> Reporter: Dennis Kieselhorst
> Assignee: Dennis Kieselhorst
> Priority: Minor
> Fix For: 3.3.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> See https://github.com/eclipse-ee4j/jax-ws-api/issues/46
> According to https://projects.eclipse.org/projects/ee4j.jaxws/ will be
> released on 2018-12-14.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
