[jbossws-issues] [JBoss JIRA] Issue Comment Edited: (JBWS-2696) Better logging for messages that can not be parsed
[
https://jira.jboss.org/browse/JBWS-2696?page=com.atlassian.jira.plugin.sy...
]
Alessio Soldano edited comment on JBWS-2696 at 11/19/10 5:49 AM:
-----------------------------------------------------------------
I see that some lines above the mentioned check in MessageFactoryImpl there's a block
for printing the provided inputstream contents to the logs. It is protected by a
log.isTraceEnabled(), so enabling the trace log level for the org.jboss.ws.core.soap
package should do the trick.
Darran, feel free to reopen if I didn't get what you needed here correctly.
was (Author: alessio.soldano(a)jboss.com):
I see that some lines above the mentioned check in MessageFactoryImpl there's a
block for printing the provided inputstream contents to the logs. It is protected by a
log.isTraceEnabled(), so enabling the trace log level for the org.jboss.ws.core.soap
package should do the trick.
Darran, feel free to reopen if I did get what you needed here correctly.
Better logging for messages that can not be parsed
--------------------------------------------------
Key: JBWS-2696
URL: https://jira.jboss.org/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: Alessio Soldano
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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira