[ 
https://issues.apache.org/jira/browse/LOG4J2-31?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12867807#action_12867807
 ] 

Ralph Goers commented on LOG4J2-31:
-----------------------------------

This is implemented on my experimental branch

> The Logging API should support a Message object
> -----------------------------------------------
>
>                 Key: LOG4J2-31
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-31
>             Project: Log4j 2
>          Issue Type: New Feature
>          Components: API
>            Reporter: Ralph Goers
>             Fix For: 0.1
>
>
> RFC 5424 defines StructuredData. While implementing this for Logback it was 
> found that making SLF4J support a Message interface and then providing 
> Message definitions for a "SimpleMessage" (message text only), 
> "ParamaterizedMessage" (message plus substitution parameters) and 
> StructuredDataMessage (a message that allows the formatted message to conform 
> to RFC 5424) allows the API to be easily extendable with new Message types 
> and makes it more efficient to pass them through the logging implementation.
> Log4j 2.0 should incorporate this into both the API and the implementation. 
> This will allow for easy implementation of a SyslogAppender that conforms 
> with the new Syslog specification (see http://tools.ietf.org/html/rfc5424) as 
> well as using the RFC 5424 as a standard layout that can be used to transport 
> messages via JMS or other protocols.
> See http://github.com/rgoers/slf4j and http://github.com/rgoers/logback for 
> examples of how I accomplished this for slf4j & logback.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to