jax-ws
  1. jax-ws
  2. JAX_WS-671

JAX-WS sends XOP messages to non-MTOM aware clients

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.1.5
    • Fix Version/s: 2.1.7
    • Component/s: runtime
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

    • Issuezilla Id:
      671

      Description

      Since JAX-WS allows normal messages and XOP encoded messages for MTOM enabled
      service, it should send non-XOP encoded messages to requests coming from
      non-MTOM aware clients.

      JAX-WS can find about the client is MTOM aware from the HTTP headers in the
      request. It should send normal messages if Content-Type header is not
      application/xop+xml and ACCEPT header doesn't contain application/xop+xml.

        Activity

        Hide
        scm_issue_link added a comment -

        Code changed in jax-ws-sources
        User: ramapulavarthi
        Path:
        /jax-ws-sources/jaxws-ri/rt/src/com/sun/xml/ws/encoding/SOAPBindingCodec.java (1.6.4.1)
        http://fisheye5.cenqua.com/changelog/jax-ws-sources/?cs=jaxws213:ramapulavarthi:20090207024858

        Log:
        JAX-WS-671: Don't send MTOM messages to non-MTOM aware clients though MTOM feature is enabled.
        On client, always use XOP encoding if MTOM is enabled
        On Server, use XOP encoding if either request is XOP encoded or client accepts XOP encoding.
        The logic would have been much easier if the packet has some info on if the codec is being run on server or client. To limit the changes to this file, some state is maintained in the codec.

        Show
        scm_issue_link added a comment - Code changed in jax-ws-sources User: ramapulavarthi Path: /jax-ws-sources/jaxws-ri/rt/src/com/sun/xml/ws/encoding/SOAPBindingCodec.java (1.6.4.1) http://fisheye5.cenqua.com/changelog/jax-ws-sources/?cs=jaxws213:ramapulavarthi:20090207024858 Log: JAX-WS-671: Don't send MTOM messages to non-MTOM aware clients though MTOM feature is enabled. On client, always use XOP encoding if MTOM is enabled On Server, use XOP encoding if either request is XOP encoded or client accepts XOP encoding. The logic would have been much easier if the packet has some info on if the codec is being run on server or client. To limit the changes to this file, some state is maintained in the codec.
        Hide
        scm_issue_link added a comment -

        Code changed in jax-ws-sources
        User: ramapulavarthi
        Path:
        /jax-ws-sources/jaxws-unit/testcases/mtom/issue_671/server/HelloProviderImpl.java (1.1)
        /jax-ws-sources/jaxws-unit/testcases/mtom/issue_671/server/hello.wsdl (1.1)
        /jax-ws-sources/jaxws-unit/testcases/mtom/issue_671/server/HelloImpl.java (1.1)
        /jax-ws-sources/jaxws-unit/testcases/mtom/issue_671/resources/raw.envelope (1.1)
        /jax-ws-sources/jaxws-unit/testcases/mtom/issue_671/resources/normal.envelope (1.1)
        /jax-ws-sources/jaxws-unit/testcases/mtom/issue_671/resources/gpsXml.xml (1.1)
        /jax-ws-sources/jaxws-unit/testcases/mtom/issue_671/resources/raw1.envelope (1.1)
        /jax-ws-sources/jaxws-unit/testcases/mtom/issue_671/resources/xop.envelope (1.1)
        /jax-ws-sources/jaxws-unit/testcases/mtom/issue_671/test-descriptor.xml (1.1)
        /jax-ws-sources/jaxws-unit/testcases/mtom/issue_671/client/Issue671Test.java (1.1)
        http://fisheye5.cenqua.com/changelog/jax-ws-sources/?cs=MAIN:ramapulavarthi:20090210191158

        Log:
        JAX-WS-671: Adding testcases to verify the behavior of Server Runtime when MTOM is enabled.

        Show
        scm_issue_link added a comment - Code changed in jax-ws-sources User: ramapulavarthi Path: /jax-ws-sources/jaxws-unit/testcases/mtom/issue_671/server/HelloProviderImpl.java (1.1) /jax-ws-sources/jaxws-unit/testcases/mtom/issue_671/server/hello.wsdl (1.1) /jax-ws-sources/jaxws-unit/testcases/mtom/issue_671/server/HelloImpl.java (1.1) /jax-ws-sources/jaxws-unit/testcases/mtom/issue_671/resources/raw.envelope (1.1) /jax-ws-sources/jaxws-unit/testcases/mtom/issue_671/resources/normal.envelope (1.1) /jax-ws-sources/jaxws-unit/testcases/mtom/issue_671/resources/gpsXml.xml (1.1) /jax-ws-sources/jaxws-unit/testcases/mtom/issue_671/resources/raw1.envelope (1.1) /jax-ws-sources/jaxws-unit/testcases/mtom/issue_671/resources/xop.envelope (1.1) /jax-ws-sources/jaxws-unit/testcases/mtom/issue_671/test-descriptor.xml (1.1) /jax-ws-sources/jaxws-unit/testcases/mtom/issue_671/client/Issue671Test.java (1.1) http://fisheye5.cenqua.com/changelog/jax-ws-sources/?cs=MAIN:ramapulavarthi:20090210191158 Log: JAX-WS-671: Adding testcases to verify the behavior of Server Runtime when MTOM is enabled.
        Hide
        scm_issue_link added a comment -

        Code changed in jax-ws-sources
        User: ramapulavarthi
        Path:
        /jax-ws-sources/jaxws-ri/rt/src/com/sun/xml/ws/encoding/SOAPBindingCodec.java (1.8)
        http://fisheye5.cenqua.com/changelog/jax-ws-sources/?cs=MAIN:ramapulavarthi:20090313182642

        Log:
        JAX-WS-671: Porting Mtom fix to allow non-mtom aware clients when a MTOM is enabled on server-side to trunk.

        Show
        scm_issue_link added a comment - Code changed in jax-ws-sources User: ramapulavarthi Path: /jax-ws-sources/jaxws-ri/rt/src/com/sun/xml/ws/encoding/SOAPBindingCodec.java (1.8) http://fisheye5.cenqua.com/changelog/jax-ws-sources/?cs=MAIN:ramapulavarthi:20090313182642 Log: JAX-WS-671: Porting Mtom fix to allow non-mtom aware clients when a MTOM is enabled on server-side to trunk.
        Hide
        jitu added a comment -

        Fixing it in 2.1.7

        Show
        jitu added a comment - Fixing it in 2.1.7

          People

          • Assignee:
            jax-ws-issues
            Reporter:
            ramapulavarthi
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: