[jbossws-issues] [JBoss JIRA] Updated: (JBWS-2903) MTOM/XOP root MIME part does not contain charset parameter

Alessio Soldano (JIRA) jira-events at lists.jboss.org
Thu Feb 25 06:22:10 EST 2010


     [ https://jira.jboss.org/jira/browse/JBWS-2903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alessio Soldano updated JBWS-2903:
----------------------------------

    Fix Version/s: jbossws-native-3.3.0.Beta5


> MTOM/XOP root MIME part does not contain charset parameter
> ----------------------------------------------------------
>
>                 Key: JBWS-2903
>                 URL: https://jira.jboss.org/jira/browse/JBWS-2903
>             Project: JBoss Web Services
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: jbossws-native
>    Affects Versions:  jbossws-native-3.2.2
>            Reporter: David Boeren
>            Assignee: Alessio Soldano
>             Fix For: jbossws-native-3.3.0.Beta5
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the jbossws-issues mailing list