Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-6729

MTOM/XOP root MIME part does not contain charset parameter

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • EAP_EWP 5.1.2 ER1
    • EAP_EWP 5.1.0
    • Web Services
    • None
    • Hide
      Some clients failed to parse web service responses sent from JBoss that were MTOM/XOP encoded because JBoss Web Services failed to add the "charset" parameter to the root MIME part if the used charset was different from the implicit default "ISO-8859-1". The "charset" parameter is now added to the web service response if necessary.
      Show
      Some clients failed to parse web service responses sent from JBoss that were MTOM/XOP encoded because JBoss Web Services failed to add the "charset" parameter to the root MIME part if the used charset was different from the implicit default "ISO-8859-1". The "charset" parameter is now added to the web service response if necessary.
    • Documented as Resolved Issue
    • NEW

      Web service responses sent from JBoss that are MTOM/XOP encoded cannot be parsed by some clients because the root MIME part does not contain charset parameter.

      RFC2616 Sections 14.17 and 3.7.1 state that the charset is not required unless it differs from the implicit default of "ISO-8859-1". JBossWS is encoding the root MIME part in UTF8, so the charset must be provided.

      As such, this is a bug in JBossWS.

              rhn-support-bmaxwell Brad Maxwell
              rhn-support-bmaxwell Brad Maxwell
              Eva Kopalova Eva Kopalova (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: