[
https://issues.apache.org/jira/browse/LOG4J2-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13792927#comment-13792927
]
erich oliphant commented on LOG4J2-422:
---------------------------------------
Sure it's a Spring Integration app deployed as a war/webapp. If you have STS,
it's based on one of their templates "Spring Integration Template (War). It's
deployed into the bundled tcServer dev edition 2.9 (which I think corresponds
to tomcat 7)
> 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-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
