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

Dependency javax.xml.ws/jaxws-api should be changed to the jakarta one

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Duplicate
    • 3.3.1
    • None
    • JAX-WS Runtime
    • None
    • Java 11

    • Unknown

    Description

      <dependency>
          <groupId>javax.xml.ws</groupId>
          <artifactId>jaxws-api</artifactId>
          <version>2.3.0</version>
      </dependency>
      

      This jaxws-api dependency is defined in some of the pom.xm (e.g parent/pom.xml) for JDK 9 and above.

      But this jaxws-api bundle has wrong package version exported for "javax.xml.ws.*" packages, the expected exported version is 2.3.x, but it exports the version 2.4.0. As consequence there is exception thrown on user bundle for OSGi (karaf) deployment.

      missing requirement [my-serrvice/1.0.0] osgi.wiring.package; filter:="(&(osg
      i.wiring.package=javax.xml.ws)(version>=2.4.0)(!(version>=3.0.0)))"]]
      

      The javax.xml.ws api from Jakarta is good enough has the right package version exported for OSGi scenaro.

      <dependency>
          <groupId>jakarta.xml.ws</groupId>
          <artifactId>jakarta.xml.ws-api</artifactId>
          <version>2.3.2</version>
      </dependency>
      

      For JAXB api, the Jakarta one already used for JAVA 9/10/11, so the WS api should be also changed to the Jakarta one.

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            xldai Xilai Dai
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment