[jbossws-issues] [JBoss JIRA] Updated: (JBWS-2696) Better logging for messages that can not be parsed

[Richard Opalka (JIRA)]

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

Richard Opalka updated JBWS-2696:
---------------------------------

    Fix Version/s: jbossws-native-3.3
                       (was:  jbossws-native-3.2.2)


Rescheduling - QA branches have been created

> Better logging for messages that can not be parsed
> --------------------------------------------------
>
>                 Key: JBWS-2696
>                 URL: https://jira.jboss.org/jira/browse/JBWS-2696
>             Project: JBoss Web Services
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: jbossws-native
>    Affects Versions:  jbossws-native-3.1.2
>            Reporter: Darran Lofthouse
>            Assignee: Darran Lofthouse
>             Fix For: jbossws-native-3.3
>
>
> The MessageFactoryImpl class uses for the following check for the content type of the incoming message: -
> if (isSoapContent(contentType) == false)
> {
>   throw new SOAPException("Unsupported content type: " + contentType);
> }
> For various servers even though the incoming message is not a SOAP message the message may still contain useful information that could help diagnose the failure.
> Consider adding an option to still log the payload of the incoming message.

-- 
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