I reviewed the e-mail I sent, and noticed a few places that I should clarify
a bit more. This may not be necessary, but in case it helps convey things a
little more clearly, here it is. Notice that if you remove my comments, this
is all part of one section that is complete (that admittedly had some typos
and missing grammar.)

> It is the job of the 'Layout' to format the text. The 'Layout(s)'
supposedly
> are fairly generic and delegate rendering of object data to the
> 'ObjectRenderer(s)'. This is very handy since the 'Layout' does not have
to
> understand each object that comes in.

By this I mean that a 'Layout' does not have to know how to convert every
object that it receives through the 'format(LoggingEvent)' method into a
String. A 'Layout' can have an 'ObjectRenderer(s)' return a String and
include this in the response to 'format'.

> Making an 'ObjectRenderer' to hand back a correct 'String' to the
> 'Layout'

By 'correct String' I mean a String that is compatible with the format that
the 'Layout' is intended to return. One case I indicated was comma separated
list. The other was XML format. The 'correct String' representation of an
object would be different for each of these.

> in any one of these cases is fairly trivial. It is fairly trivial to make
an
> 'ObjectRenderer' that returns ftp info in a comma separated list,

By 'ftp info' I mean an FTPCommandInfo object that was sent to the 'Logger'.
It is easy to make a specific 'ObjectRenderer' to take an object and return
a String that adheres to a certain format (i.e. comma separated list, or XML
attributes in our case.)

> or one that returns the ftp info as a set of
> xml attributes, or even one that excludes certian info the loggable object
> contains that should not be displayed. However these does not seem to be a

Typo - 'these' should have been 'there' in the sentence above

> way for these 'ObjectRenderer(s)' to coexist in log4j at the same time and
> associated with the respective 'Layout(s)'.

Clarification of sentence above - log4j does not seem to have a way to allow
multiple 'ObjectRenderer(s)' for the same object type (i.e. FTPCommandInfo
in our case) to coexist and be assigned to different 'Layout(s)' that may
require different 'String(s)'.




--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to