I tried about the same using renderer component for individual
columns...but could not reach a point.
Other alternative that I can think is instead of INSERT stmt, putting an SP
call in XML, but I have not tried it upto now
Still I feel JDBCAppender should not be totally removed.
regards,
Amandeep
-------------------------------------------------
Amandeep Midha (CHARMIE)
IT Solutions (India) Pvt. Ltd.
No. 17, South End Road,
Basavanudi
Bangalore - 560 004. India
TEL : 91-80-6657180 EXT: 2116
MOBILE: +919844048126 (Upto March 12, 2003)
FAX: 91-80-6655755
-------------------------------------------------
Ceki Gülcü
<[EMAIL PROTECTED]> To: "Log4J Developers List"
<[EMAIL PROTECTED]>
cc:
02/21/2003 Subject: RE: JDBCAppender proposal
07:24 PM
Please respond
to "Log4J
Developers
List"
By the way, there is already an alternative:
http://www.dankomannhaupt.de/projects/index.html
At 13:12 19.02.2003 -0500, you wrote:
>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:[EMAIL PROTECTED]]
>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ülcü [mailto:[EMAIL PROTECTED]]
> > Sent: Wednesday, February 19, 2003 7:30 AM
> > To: Log4J Developers List
> > Subject: RE: JDBCAppender proposal
> >
> >
> > 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: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> > >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: [EMAIL PROTECTED]
> > >For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > >-------------------------------------------------------------
> > ---------------
> > >---
> > >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
> > [EMAIL PROTECTED] Thank you
> > >
> > >---------------------------------------------------------------------
> > >To unsubscribe, e-mail: [EMAIL PROTECTED]
> > >For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > >-------------------------------------------------------------
> > ------------------
> > >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
> > [EMAIL PROTECTED] Thank you
> > >
> > >---------------------------------------------------------------------
> > >To unsubscribe, e-mail: [EMAIL PROTECTED]
> > >For additional commands, e-mail: [EMAIL PROTECTED]
> >
> > --
> > Ceki
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>
>
-------------------------------------------------------------------------------
>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 [EMAIL PROTECTED] Thank you
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
--
Ceki
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
