cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Schneider (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CXF-6442) Possible uses contraint violation because of different servlet API versions
Date Fri, 05 Jun 2015 13:58:01 GMT

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

Christian Schneider resolved CXF-6442.
--------------------------------------
    Resolution: Fixed

> Possible uses contraint violation because of different servlet API versions
> ---------------------------------------------------------------------------
>
>                 Key: CXF-6442
>                 URL: https://issues.apache.org/jira/browse/CXF-6442
>             Project: CXF
>          Issue Type: Bug
>          Components: Transports
>    Affects Versions: 3.1.0
>            Reporter: Christian Schneider
>            Assignee: Christian Schneider
>             Fix For: 3.1.1
>
>
> The cxf-http feature load the servlet API 3.0 while pax web load servlet API 3.1. So
if cxf-http is loaded before the http feature it might bind to the lower API version. If a
user bundle then uses CXF and the Servlet API there can be a uses contraint violation. 
> I had this with the xkms features at least once. Most times the problem did not appear
though.
> I propose to solve this by adding a cxf-http-client feature which only installs the servlet
API 3.0 and switch the default cxf-http feature to depend on http again. So users still can
select to use the slim version but the default case will not be prone to the uses constraint
violation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message