You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "George McCone (Jira)" <ji...@apache.org> on 2019/09/13 14:34:00 UTC

[jira] [Closed] (GERONIMO-6750) JWS Spec version exported as 2.0

     [ https://issues.apache.org/jira/browse/GERONIMO-6750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

George McCone closed GERONIMO-6750.
-----------------------------------
    Resolution: Invalid

I was mistaken in my understanding of the specification. I assumed that if it didn't exist on Maven Central then it must not exist. Romain was kind enough to show me where to find the specification versions.

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