Uploaded image for project: 'JBoss Web Services'
  1. JBoss Web Services
  2. JBWS-3857

Wrong content type (text/xml) in outgoing multipart SOAPMessage (expected multipart/related; ...)

    XMLWordPrintable

    Details

    • Steps to Reproduce:
      Hide

      Steps to Reproduce:
      1. Create test app which will send multipart SOAPMessage (using javax.xml.soap API).
      2. Catch http communication and watch message content type.

      Actual results:
      Content type is text/xml.

      Expected results:
      Content type should be multipart/related; ...

      Show
      Steps to Reproduce: 1. Create test app which will send multipart SOAPMessage (using javax.xml.soap API). 2. Catch http communication and watch message content type. Actual results: Content type is text/xml. Expected results: Content type should be multipart/related; ...
    • Bugzilla Update:
      Perform

      Description

      Clone of EAP6 issue https://bugzilla.redhat.com/show_bug.cgi?id=1167348 - WF is also susceptible.

      Description of problem:
      There is wrong content type (text/xml) in multipart SOAPMessage when sending it using javax.xml.soap API. So target system is unable to parse it.

      How reproducible:
      always

      Additional info:
      It's also wrong in EAP 6.2.
      EAP 6.1 is OK.

      There is a patch attached in BZ-1167348 for JBossWS CXF 4.3.3. The same fix should be also applied to JBossWS CXF 5.0.0 which is used by Wildfly.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  rsearls r searls
                  Reporter:
                  thofman Tomas Hofman
                  Tester:
                  Martin Swiech
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: