[
https://issues.apache.org/jira/browse/GERONIMO-6750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16927619#comment-16927619
]
George McCone commented on GERONIMO-6750:
-----------------------------------------
So after doing some digging around, it looks like [eclipse-ee4j repo is
preparing to release|[https://github.com/eclipse-ee4j/jws-api/issues/29]] a
version 2.1 of this api as
<dependency>
<groupId>jakarta.jws</groupId>
<artifactId>jakarta.jws-api</artifactId>
<version>2.1.0</version>
</dependency>
Is this going to cause a problem with CXF since the Geronimo version is 2.0 not
2.1?
> JWS Spec version exported as 2.0
> --------------------------------
>
> Key: GERONIMO-6750
> URL: https://issues.apache.org/jira/browse/GERONIMO-6750
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: specs
> Reporter: George McCone
> Priority: Major
>
> The geronimo-ws-metadata_2.0_spec artifact is being generated with a bundle
> manifest that declares the javax.jws package versions as 2.0.
> This is problematic as there is no offical release of the JWS API with
> version 2.0, instead the latest is version is 1.1.x.
> We have a project that creates bundles that must run in environments using
> both Glassfish and CXF.
> Using the following dependency, everything works fine in the Glassfish
> environment
> <dependency>
> <groupId>javax.jws</groupId>
> <artifactId>javax.jws-api</artifactId>
> <version>1.1</version>
> <scope>provided</scope>
> </dependency>
> But when we try running these bundles in karaf using the CXF feature, they
> fail to resolve as the JWS package version provided by Geronimo and used by
> the CXF feature is exporting 2.0.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
