Okay. Absent any other feedback, I'm going to remove the
DriverManagerConnectionSource.
N
On Feb 6, 2014, at 4:03 PM, Matt Sicker wrote:
> It'd be cleaner to just remove it. Perhaps we could include in log4j-samples
> a sort of rudimentary connection pool factory using dbcp?
>
>
> On 5 Febru
It'd be cleaner to just remove it. Perhaps we could include in
log4j-samples a sort of rudimentary connection pool factory using dbcp?
On 5 February 2014 18:07, Remko Popma wrote:
>
>
> On Thursday, February 6, 2014, Nick Williams <
> nicho...@nicholaswilliams.net> wrote:
>
>>
>> On Feb 5, 2014
On Thursday, February 6, 2014, Nick Williams
wrote:
>
> On Feb 5, 2014, at 5:52 PM, Remko Popma wrote:
>
>
>
> On Thursday, February 6, 2014, Nick Williams <
> nicho...@nicholaswilliams.net>
> wrote:
>
>> Guys,
>>
>> Currently, the JDBCAppender allows users to specify a mechanism for
>> connectin
On Feb 5, 2014, at 5:52 PM, Remko Popma wrote:
>
>
> On Thursday, February 6, 2014, Nick Williams
> wrote:
> Guys,
>
> Currently, the JDBCAppender allows users to specify a mechanism for
> connecting to the database using one of three options:
>
> - DataSourceConnectionSource: Looks up a J
On Thursday, February 6, 2014, Nick Williams
wrote:
> Guys,
>
> Currently, the JDBCAppender allows users to specify a mechanism for
> connecting to the database using one of three options:
>
> - DataSourceConnectionSource: Looks up a JNDI data source
> - FactoryMethodConnectionSource: User specif
I think if we added a DBCP/CP dependency version, that should be a separate
or optional module/plugin. It seems like it'd be useful as a demonstration
for a connection source factory.
On 5 February 2014 16:46, Nick Williams wrote:
> Guys,
>
> Currently, the JDBCAppender allows users to specify a
Another thing to consider is how this would look from a configuration POV. It
would be nice to avoid code for most of it. I suppose that's what JNDI is for
but you still have to populate the store.
Gary
Original message
From: Nick Williams
Date:02/05/2014 17:46 (GMT-05:00
