You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "Gary Gregory (JIRA)" <ji...@apache.org> on 2018/01/13 04:31:01 UTC
[jira] [Reopened] (LOG4J2-2185) Add a simple
DriverManagerConnectionSource that uses JDBC's
DriverManager#getConnection(String, String, String)
[ https://issues.apache.org/jira/browse/LOG4J2-2185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Gregory reopened LOG4J2-2185:
----------------------------------
> Add a simple DriverManagerConnectionSource 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
> Fix For: 2.10.1
>
>
> 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
(v6.4.14#64029)