jax-ws
  1. jax-ws
  2. JAX_WS-978

Bug 9780051 - BP R1019 A RECEIVER MUST IGNORE THE ENCODING PSEUDO--ATTRIBUTE OF THE XML DECLAR

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Duplicate
    • Affects Version/s: current
    • Fix Version/s: None
    • Component/s: runtime
    • Labels:
      None

      Description

      Migration of existing WebLogic / Oracle bug: https://bug.oraclecorp.com/pls/bug/webbug_edit.edit_info_top?rptno=9780051

      Original description:
      Service:
      @ http://webservice.bea.com:7001/MTOM_Service_Soap11MtomUtf16BP12NoAddressing/CustomBinding_IMtomExtendedContract?wsdl

      We have issues in determining xml encoding of UTF-16 request.

      When the request like the below

      ------=_Part_0_11145468.1217087070812
      Content-Type: application/xop+xml;charset=UTF-16LE;
      type="application/soap+xml"
      Content-Transfer-Encoding: binary
      Content-ID: <c3cfd155290f401bbfe8c2a3fc4687d5>

      < ? x m l v e r s i o n = " 1 . 0 " e n c o d i n g = " U T F

      • 1 6 E " ? > < SOAP />

      We process the request correctly; but when the prolog is not there, we fail
      with


      0903 echoBinaryAsString FAILED +

      EXCEPTION: Couldn't create SOAP message due to exception: XML reader error:
      com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character
      (CTRL-CHAR, code 0) in prolog, after '<'.
      at [row,col

      {unknown-source}

      ]: [1,2]
      [Ljava.lang.StackTraceElement;@36e636e6
      ------

      Original fix:
      http://tamarac.us.oracle.com/describe.php?change=1344089.

        Activity

        Hide
        naijun.sheng added a comment -

        Jaxws already contains this bug's fix. No need to merge jaxws-wls change.

        Show
        naijun.sheng added a comment - Jaxws already contains this bug's fix. No need to merge jaxws-wls change.
        Hide
        haroldcarr added a comment -

        Are the fixes that jaxws22 has identical in functionality to the fixes you would have applied?

        Show
        haroldcarr added a comment - Are the fixes that jaxws22 has identical in functionality to the fixes you would have applied?
        Hide
        naijun.sheng added a comment -

        Yes, they are identical in functionality.

        Show
        naijun.sheng added a comment - Yes, they are identical in functionality.
        Hide
        haroldcarr added a comment -

        OK. It would be good to find out if there is an existing JAX-WS RI bug for this bug to link to and close as a duplicate.

        Show
        haroldcarr added a comment - OK. It would be good to find out if there is an existing JAX-WS RI bug for this bug to link to and close as a duplicate.
        Hide
        naijun.sheng added a comment -

        This bug is a duplicated one. JAXWS RI already had a bug to fix this issue: http://java.net/jira/browse/JAX_WS-752

        Show
        naijun.sheng added a comment - This bug is a duplicated one. JAXWS RI already had a bug to fix this issue: http://java.net/jira/browse/JAX_WS-752
        Hide
        naijun.sheng added a comment -
        Show
        naijun.sheng added a comment - It is duplicate with http://java.net/jira/browse/JAX_WS-752

          People

          • Assignee:
            Unassigned
            Reporter:
            naijun.sheng
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: