Log4j 2
  1. Log4j 2
  2. LOG4J2-31

The Logging API should support a Message object


    • Type: New Feature New Feature
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.0-alpha1
    • Component/s: API
    • Labels:


      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.


        Ralph Goers made changes -
        Field Original Value New Value
        Status Open [ 1 ] Closed [ 6 ]
        Assignee Ralph Goers [ ralph.goers@dslextreme.com ]
        Fix Version/s 2.0-alpha1 [ 12320347 ]
        Fix Version/s 0.1 [ 12313077 ]
        Resolution Fixed [ 1 ]
        Ralph Goers created issue -


          • Assignee:
            Ralph Goers
            Ralph Goers
          • Votes:
            0 Vote for this issue
            0 Start watching this issue


            • Created: