geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Romain Manni-Bucau (Jira)" <j...@apache.org>
Subject [jira] [Commented] (GERONIMO-6750) JWS Spec version exported as 2.0
Date Wed, 11 Sep 2019 04:46:00 GMT

    [ https://issues.apache.org/jira/browse/GERONIMO-6750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16927250#comment-16927250
] 

Romain Manni-Bucau commented on GERONIMO-6750:
----------------------------------------------

 Hi George,

 

2.0 exists: [https://jcp.org/en/jsr/detail?id=224]

GroupId of the RI is javax.xml.ws

So it looks right to me

 

Romain

> 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)

Mime
View raw message