[
https://issues.apache.org/jira/browse/LOG4J2-2185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16331682#comment-16331682
]
ASF subversion and git services commented on LOG4J2-2185:
---------------------------------------------------------
Commit 96c3bcab0c91d4be2d6e65ecfb022bfa0cd124bb in logging-log4j2's branch
refs/heads/master from [~garydgregory]
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=96c3bca ]
[LOG4J2-2185] Add a simple JDBC DriverManager-based ConnectionSource
that uses JDBC's DriverManager#getConnection(String, String, String):
Open up class for subclassing from log4j-jdbc-dbcp2 (which is not
committed yet but working locally.)
> Add a simple JDBC DriverManager-based ConnectionSource that uses JDBC's
> DriverManager#getConnection(String, String, String)
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: LOG4J2-2185
> URL: https://issues.apache.org/jira/browse/LOG4J2-2185
> Project: Log4j 2
> Issue Type: New Feature
> Components: Appenders
> Reporter: Gary Gregory
> Assignee: Gary Gregory
> Priority: Major
> Fix For: 2.11
>
>
> Add a simple DriverManagerConnectionSource that uses JDBC's
> {{DriverManager#getConnection(String, String, String)}}
> {code:java}
> /**
> * A {@link ConnectionSource} that uses a JDBC connection string, a user
> name, and a password to call
> * {@link DriverManager#getConnection(String, String, String)}.
> * <p>
> * This plugin does not provide any connection pooling unless it is available
> through the connection string and driver
> * itself. This handy to get you off the ground without having to deal with
> JNDI.
> * </p>
> */
> @Plugin(name = "DriverManager", category = Core.CATEGORY_NAME, elementType =
> "connectionSource", printObject = true)
> public final class DriverManagerConnectionSource implements ConnectionSource
> {code}
> This connection source also supports passing in properties for more complex
> configurations.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
