*Thank you for both replies. There is no similar issue in Bugzilla, but the javadoc of JDBCAppender says*
*WARNING: This version of JDBCAppender is very likely to be completely replaced in the future. Moreoever, it does not log exceptions*. To me it seems the original developer wasn't satisfied either. I will submit my version next week when it is passed my tests. P On Fri, Nov 19, 2010 at 4:45 PM, Jacob Kjome <[email protected]> wrote: > I would suggest searching through Bugzilla to see if there is an > enhancement issue > that would be a fit for your suggested modifications. If so, read up on > that and > add your stuff as appropriate. Otherwise, create a new enhancement issue > and > attach your patch, along with your expressed intent to donate the changes > to the > Apache Foundation. > > Note that any changes must be backward compatible with the existing code so > behavior does not change (for the worse) for existing users/extenders. > > Jake > > On 11/19/2010 5:48 AM, Peter Szanto wrote: > > Hi All > > > > I plan to optimize the JDBCAppender to use batch updates and do the JDBC > > part asynchronously. How is it possible to contribute it back to the > > community? (i.e.: became a commiter) > > > > Thanks > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
