Mailing-List: contact log4j-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Log4J Developers List" <log4j-dev@jakarta.apache.org>
Message-ID: 
 <47595B04C59BDE4592F43A57C9ED8FAC8FE14D@MLVV9MLE.ww005.siemens.net>
From: Lutz Michael <michael.h.lutz@siemens.com>
To: "'Log4J Developers List'" <log4j-dev@jakarta.apache.org>
Subject: RE: JDBCAppender proposal
Date: Wed, 19 Feb 2003 13:12:49 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


Sounds good.
I have no problem if details change, I was just concerned if the entire
support for JDBC might have been dropped.
Thanks a lot for your responses.


-----Original Message-----
From: Mark Womack [mailto:mwomack@bevocal.com]
Sent: Wednesday, February 19, 2003 1:07 PM
To: 'Log4J Developers List'
Subject: RE: JDBCAppender proposal


Mike,

I second Ceki on this.  It is still in 1.2.8, and it looks like it is going
to get some major attention in v1.3.  So, I wouldn't worry too much.  But=
 it
does sound like it's features/method signature will be changing in v1.3
(depending on the extent of the re-write), but you will get plenty of=
 notice
to adjust.

Ceki, what about doing the rewrite in the sandbox?

-Mark

> -----Original Message-----
> From: Ceki G=FClc=FC [mailto:ceki@qos.ch]
> Sent: Wednesday, February 19, 2003 7:30 AM
> To: Log4J Developers List
> Subject: RE: JDBCAppender proposal
>=20
>=20
> Mike,
>=20
> There is no need to worry. JDBCAppender will have a=20
> replacement in version=20
> 1.3. Moreover, it was not removed in 1.2.8.
>=20
> At 10:01 19.02.2003 -0500, you wrote:
>=20
>=20
> >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=20
> how to use the
> >JDBC Appender, and there are plans to use it in production. =20
> I have to think
> >this situation is common.
> >
> >Removing an Appender entirely - isn't this a major backward=20
> compatibility
> >issue?  I'm just uneasy removing it from the core Log4j=20
> product without an
> >immediate replacement.
> >
> >Unfortunately, I don't have enough expertise in JDBC to add=20
> value on the
> >development effort, and for that I apologize.  If I had the=20
> 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=20
> 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=20
> 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=20
> ideas for evolving
> >this class, and others have spoken up as well.  Sounds like=20
> it needs the
> >ability to support different jdbc driver behaviors, clob's,=20
> etc.  It seems
> >that this appender is popular with the log4j user community,=20
> so I think it
> >is right for it to be given some needed attention and upgrades.
> >
> >Interested developers, demonstrating interest, proposals,=20
> 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=20
> Medical Solutions
> >
> >Health Services Corporation and are intended only for the=20
> addressee(s).
> >The information contained herein may include trade secrets=20
> or privileged or
> >otherwise confidential information.  Unauthorized review, forwarding,
> >printing,
> >copying, distributing, or using such information is strictly=20
> prohibited and
> >may
> >be unlawful.  If you received this message in error, or have=20
> reason to
> >believe
> >you are not authorized to receive it, please promptly delete=20
> this message
> >and
> >notify the sender by e-mail with a copy to=20
> 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=20
> Medical Solutions
> >Health Services Corporation and are intended only for the=20
> addressee(s).
> >The information contained herein may include trade secrets=20
> or privileged or
> >otherwise confidential information.  Unauthorized review,=20
> forwarding,=20
> >printing,
> >copying, distributing, or using such information is strictly=20
> prohibited=20
> >and may
> >be unlawful.  If you received this message in error, or have=20
> reason to=20
> >believe
> >you are not authorized to receive it, please promptly delete=20
> this message and
> >notify the sender by e-mail with a copy to=20
> 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
>=20
> --
> Ceki=20
>=20
>=20
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: log4j-dev-help@jakarta.apache.org
>=20

---------------------------------------------------------------------
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=20
Health Services Corporation and are intended only for the addressee(s). =20
The information contained herein may include trade secrets or privileged or=
=20
otherwise confidential information.  Unauthorized review, forwarding,=
 printing,=20
copying, distributing, or using such information is strictly prohibited and=
 may=20
be unlawful.  If you received this message in error, or have reason to=
 believe=20
you are not authorized to receive it, please promptly delete this message=
 and=20
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