Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8051407

Re-examine dependency from JAX-WS to java.rmi.Remote and RemoteException

    Details

    • Type: Bug
    • Status: Closed
    • Priority: P3
    • Resolution: Duplicate
    • Affects Version/s: 9
    • Fix Version/s: None
    • Component/s: xml

      Description

      There are static references from JAX-WS to java.rmi.Remote and java.rmi.RemoteException.

      com.sun.xml.internal.ws.model.RuntimeModeler -> java.rmi.RemoteException (java.rmi)

      com.sun.tools.internal.ws.processor.modeler.annotation.WebServiceAp -> java.rmi.Remote (java.rmi)
      com.sun.tools.internal.ws.processor.modeler.annotation.WebServiceAp -> java.rmi.RemoteException (java.rmi)

      Below are some references Yarda and Miroslav found.
      1. JSR-224, section 3.7: "Service specific exceptions are defined as all checked exceptions except java.rmi.RemoteException and its subclasses.

      Conformance (java.lang.RuntimeExceptions and java.rmi.RemoteExceptions):

      java.lang.RuntimeException and java.rmi.RemoteException and their subclasses MUST NOT be treated as service specific exceptions and MUST NOT be mapped to WSDL.”

      2. JAX-WS spec

      B.6 Changes Since Early Draft 3
      • Removed references to the RMI classes that JAX-RPC 1.1 used to denote remoteness, since their role
      is now taken by annotations: java.rmi.Remote and java.rmi.RemoteException.

      This issue is to re-examine if the dependency to RMI should be needed when the user code has a dependency on RMI and confirm if JAX-WS doesn't require RMI to present for applications that don't use RMI.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                ljungman Lukáš Jungmann
                Reporter:
                mchung Mandy Chung
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: