logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ceki Gülcü <c...@qos.ch>
Subject RE: JDBCAppender proposal
Date Wed, 19 Feb 2003 15:29:37 GMT
Mike,

There is no need to worry. JDBCAppender will have a replacement in version 
1.3. Moreover, it was not removed in 1.2.8.

At 10:01 19.02.2003 -0500, you wrote:


>I just wanted to express concern about ripping it out (even if it's a
>temporary move) without a replacement.
>
>I've got existing documentation at my company telling people how to use the
>JDBC Appender, and there are plans to use it in production.  I have to think
>this situation is common.
>
>Removing an Appender entirely - isn't this a major backward compatibility
>issue?  I'm just uneasy removing it from the core Log4j product without an
>immediate replacement.
>
>Unfortunately, I don't have enough expertise in JDBC to add value on the
>development effort, and for that I apologize.  If I had the expertise, I'd
>jump right in on my own time.
>
>But ... please don't let us hanging on this.
>
>Mike
>
>
>-----Original Message-----
>From: Lutz Michael
>Sent: Wednesday, February 19, 2003 9:28 AM
>To: 'Log4J Developers List'
>Subject: RE: JDBCAppender proposal
>
>
>
>
>Mark,
>
>Does this mean that when someone downloads Log4j 1.2.8, the JDBC Appender
>wouldn't be included?
>
>
>Mike
>
>
>-----Original Message-----
>From: mwomack@apache.org [mailto:mwomack@apache.org]
>Sent: Wednesday, February 19, 2003 1:12 AM
>To: Log4J Developers List
>Subject: JDBCAppender proposal
>
>
>I propose that we place the current version of
>o.a.log4j.jdbc.JDBCAppender.java into the log4j-sandbox (I don't know if we
>should remove it altogether from the v1.3 release?).  In doing so,
>interested log4j developers need to step forward to begin the task of
>continuing its development.  I know Kevin Steppe had more ideas for evolving
>this class, and others have spoken up as well.  Sounds like it needs the
>ability to support different jdbc driver behaviors, clob's, etc.  It seems
>that this appender is popular with the log4j user community, so I think it
>is right for it to be given some needed attention and upgrades.
>
>Interested developers, demonstrating interest, proposals, and ability can be
>granted committer rights to the sandbox cvs.
>
>Once JDBCAppender reaches a stable point of evolution, we can vote to
>re-admit it to the core release.
>
>+1
>
>-Mark
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: log4j-dev-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: log4j-dev-help@jakarta.apache.org
>
>----------------------------------------------------------------------------
>---
>This message and any included attachments are from Siemens Medical Solutions
>
>Health Services Corporation and are intended only for the addressee(s).
>The information contained herein may include trade secrets or privileged or
>otherwise confidential information.  Unauthorized review, forwarding,
>printing,
>copying, distributing, or using such information is strictly prohibited and
>may
>be unlawful.  If you received this message in error, or have reason to
>believe
>you are not authorized to receive it, please promptly delete this message
>and
>notify the sender by e-mail with a copy to CSOffice@smed.com.  Thank you
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: log4j-dev-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: log4j-dev-help@jakarta.apache.org
>
>-------------------------------------------------------------------------------
>This message and any included attachments are from Siemens Medical Solutions
>Health Services Corporation and are intended only for the addressee(s).
>The information contained herein may include trade secrets or privileged or
>otherwise confidential information.  Unauthorized review, forwarding, 
>printing,
>copying, distributing, or using such information is strictly prohibited 
>and may
>be unlawful.  If you received this message in error, or have reason to 
>believe
>you are not authorized to receive it, please promptly delete this message and
>notify the sender by e-mail with a copy to CSOffice@smed.com.  Thank you
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: log4j-dev-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: log4j-dev-help@jakarta.apache.org

--
Ceki 


---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: log4j-dev-help@jakarta.apache.org


Mime
View raw message