Uploaded image for project: 'CXF'
  1. CXF
  2. CXF-6442

Possible uses contraint violation because of different servlet API versions

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 3.1
    • Fix Version/s: 3.1.1
    • Component/s: Transports
    • Labels:
      None
    • Estimated Complexity:
      Unknown

      Description

      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.

        Attachments

          Activity

            People

            • Assignee:
              cschneider Christian Schneider
              Reporter:
              cschneider Christian Schneider
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: