I found something last night I want to modify to make = extending/wrapping the Java listener process easier. When it is done = I'll send you the code. =20
My goals are to enhance the Java portion to allow easy integration into = larger custom J2EE projects with their own Log4J frameworks, and add MDC = functionality to PL/SQL that can be passed to Java and used in deciding = which Logger to use and for output in Appender layouts.=20 My company has approved releasing these mods/enhancements as open source = - by design my changes are generic and hopefully useful to other people. -----Original Message----- From: MOULARD Guillaume Sent: Wednesday, February 04, 2004 7:31 AM To: Greg Woolsey Cc: [EMAIL PROTECTED] Subject: RE : [log4plsql] Would these mods be useful? Greg,=20 =20 Good news, I'm verry happy by you proposition. Could you send me a copy of yours code. Regards,=20 Guillaume Moulard=20 [EMAIL PROTECTED] Project : LOG4PLSQL : Oracle Database Loggin tools see : http://log4plsql.sourceforge.net/ =20 -----Message d'origine----- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Envoy=E9 : mercredi 4 f=E9vrier 2004 00:00 =C0 : [EMAIL PROTECTED] Objet : [log4plsql] Would these mods be useful? I have modified version 3.1b (Nov. 12, 2003) with the following functionality. I don't know the status of current development, but these are things we need in our project, beyond the original features in 3.1b. I'm willing to share them with anyone who may want them, and/or incorporate them into the main log4Plsql development: * MDC support in Log4Plsql analogous to the MDC functionality in Log4J (fast implementation via strings only, no complex data structures) * Pipes are per-user. Install Log4Plsql in multiple schemas and each can have it's own pipe. Modify to be authid current user and you only need one install. * Java background process completely re-written to be much faster (SQLJ does one JDBC call per pipe message component - very expensive). Instead, I have a PL/SQL procedure that, when called, reads the next pipe message or times out, and returns each value as an OUT parameter. This includes the above mentioned open-ended MDC functionality, without using collections. * Java background process class is extensible to add extra logic around determining the logger name. Default is section name, but subclasses can use any message or environment values to derive a logger name and instantiate it. * As indicated above, the java background process handles configuring MDC fields from the database for use in Log4J Appender layouts. * The Java Runnable class that listens for messages on a pipe can be started from any other process instead. It's constructor simply takes a Connection object and optional base Logger name. =20 * The PL/SQL procedure that reads the pipe gets the pipe name from the session user name and a PLOG constant, so Java only needs a connection, nothing more. My project will be using this version to seamlessly integrate PL/SQL log messages with Java log messages in the same log file(s) for easy retrieval and management. ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ Log4plsql-all-info mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/log4plsql-all-info log4plsq : http://log4plsql.sourceforge.net Yahoo! Mail : votre e-mail personnel et gratuit qui vous suit partout ! Cr�ez votre Yahoo! Mail sur http://fr.benefits.yahoo.com/ ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ Log4plsql-all-info mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/log4plsql-all-info log4plsq : http://log4plsql.sourceforge.net
