[
https://issues.apache.org/jira/browse/CXF-4392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Freeman Fang reassigned CXF-4392:
---------------------------------
Assignee: Freeman Fang
> Easier customization of log messages in Logging[In|Out]Interceptor
> ------------------------------------------------------------------
>
> Key: CXF-4392
> URL: https://issues.apache.org/jira/browse/CXF-4392
> Project: CXF
> Issue Type: Improvement
> Components: Core
> Affects Versions: 2.6.1
> Reporter: Tore Eide Andersen
> Assignee: Freeman Fang
> Attachments: CXF-4392-customized-logging-format.patch
>
>
> We're using LoggingInInterceptor and LoggingOutInterceptor to produce logs
> for use in debugging issues in our services.
> Although we're very happy with the features they provide, we find it a bit
> difficult to tweak what information is being logged and the format of the log.
> Some of our clients would like more or less info to be logged, some would
> like everything in one line, wrapped in XML.
> Specifically, it would be nice if the code fragment in the
> LoggingInInterceptor.logging() and LoggingOutInterceptor.LogWriter.close()
> methods which produces the log message string was extracted to separate
> overridable methods in Logging[In|Out]Interceptor, like this:
> protected String formatMessage(LoggingMessage message) {
> // Use toString as default:
> return message.toString();
> }
> Another option is to add a factory method for the LoggingMessage such that we
> could override the toString method.
> Or perhaps there are even better ways to meet the need of customized logging
> formats?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
