Christoph Läubrich created CXF-9163:
---------------------------------------
Summary: OSGI Problems with cxf-rt-frontend-jaxws
Key: CXF-9163
URL: https://issues.apache.org/jira/browse/CXF-9163
Project: CXF
Issue Type: Bug
Affects Versions: 4.0.2, 4.0.0
Reporter: Christoph Läubrich
When adding cxf-rt-frontend-jaxws as OSGI bundle one get the following error:
”Missing requirement: org.apache.cxf.cxf-rt-frontend-jaxws 4.1.3 requires
'java.package; org.apache.cxf.jaxws.blueprint 0.0.0' but it could not be found”
With version cxf-4.0.0 and above the OSGI bundle activator was removed from
cxf-rt-frontend-jaxws, though it is still referenced in the pom for versions
4.0.2 and above. Please also refer to
https://issues.apache.org/jira/browse/CXF-8879 where the OSGI bundle manifest
were broken since version 4.
Please also see
https://github.com/apache/cxf/blob/cxf-4.1.3/rt/frontend/jaxws/pom.xml#L50
{code}<cxf.export.service>
org.apache.aries.blueprint.NamespaceHandler;osgi.service.blueprint.namespace=”http://cxf.apache.org/blueprint/jaxws”
</cxf.export.service>
<cxf.bundle.activator>org.apache.cxf.jaxws.blueprint.Activator</cxf.bundle.activator>{code}
Also all osgi version properties needs updates. They do not match the versions
of the used dependencies.
See https://github.com/apache/cxf/blob/main/parent/pom.xml#L68
Version mismatch Example:
cxf.osgi.jakarta.xml.ws.version = [3,4)
cxf.jakarta.wsapi.version = 4.0.2
Both refer to
<groupId>jakarta.xml.ws</groupId>
<artifactId>jakarta.xml.ws-api</artifactId>
Maybe you should think about using maven plugins for the MANIFEST generation
like:
-
https://felix.apache.org/documentation/subprojects/apache-felix-maven-bundle-plugin-bnd.html
-
https://github.com/bndtools/bnd/tree/master/maven-plugins/bnd-maven-plugin#bnd-process-goal
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
