logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nick Williams (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LOG4J2-422) DriverManager for JDBC Appender should have argument for explicit Driver class
Date Fri, 11 Oct 2013 18:34:42 GMT

    [ https://issues.apache.org/jira/browse/LOG4J2-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13792922#comment-13792922
] 

Nick Williams commented on LOG4J2-422:
--------------------------------------

Hmmmm. That's odd. Can you tell me a bit about your application/environment? Is this a web
application, and if so what application server are you using? Details like that would be helpful.

> DriverManager for JDBC Appender should have argument for explicit Driver class
> ------------------------------------------------------------------------------
>
>                 Key: LOG4J2-422
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-422
>             Project: Log4j 2
>          Issue Type: Improvement
>          Components: Appenders
>    Affects Versions: 2.0-beta9
>            Reporter: erich oliphant
>            Assignee: Nick Williams
>
> I had a situation where the DriverManager was unable to properly load the jdbc driver
(Oracle) via url resolution alone.  The DriverManager doesnt' currently allow you to explicitly
specify the the driver.  I resolved my situation by creating my own that accepts a driver
parameter, but it seems like this should be added to the core 



--
This message was sent by Atlassian JIRA
(v6.1#6144)

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org


Mime
View raw message