On Apr 28, 2005, at 1:42 PM, Dave Pawson wrote:
On Wed, 2005-04-27 at 15:16 -0500, Curt Arnold wrote:
<snip/>Tell me why please?
Am I making sense?
Okay, I wanted to make sure that you wanted what I think that I would want in that situation.
If I were to add that, my initial approach would be to add a new layout
(say XSLTLayout) that would use the javax.xml.transform API's (present
in JDK 1.4, not sure when introduced). The transform would be fired
once for each LoggingEvent.
To allow you to control the element names, namespaces, position of information, etc, you would need some sort of template language and since XSLT is a W3C recommendation, there is a standard javax API, and an implementation bundled with newer JVM's, it seems like a better choice than creating a new template language.
One of the items on my to-do list is to improve the JoranConfigurator's
configurators handling of foreign namespaces within a configuration
file. The XSLTLayout would likely be a very practical test whether I
got that right. What I envision would be to embed the XSLT transform
within the XML configuration for the XSLTLayout.
I can't see any need for a transform? All I'm asking for is to add (or not) some of the information already present. Not to transform it? I can do that when post processing the xml output?
If you are post-processing, you can just use the XMLLayout since all the information is already there, just maybe not in the form that you would prefer. The only justification for a new layout is if we wanted the initially write the log file as if it had already been transformed.
Don't hold your breath for anything. The only reason that I would even consider developing an XSLT based layout at the moment would be as a test of work in need to do on the JoranConfigurator.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
