[
https://issues.apache.org/jira/browse/JENA-646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13910175#comment-13910175
]
Rob Vesse commented on JENA-646:
--------------------------------
One workaround for this is to leverage the {{jdbc.drivers}} system property
detailed in the {{DriverManager}} documentation:
{quote}
As part of its initialization, the DriverManager class will attempt to load the
driver classes referenced in the "jdbc.drivers" system property. This allows a
user to customize the JDBC Drivers used by their applications. For example in
your ~/.hotjava/properties file you might specify:
jdbc.drivers=foo.bah.Driver:wombat.sql.Driver:bad.taste.ourDriver
{quote}
So for Jena JDBC one could set this like so:
{noformat}
jdbc.drivers=org.apache.jena.jdbc.tdb.TDBDriver:org.apache.jena.jdbc.remote.RemoteEndpointDriver:org.apache.jena.jdbc.mem.MemDriver
{noformat}
> JDBC drivers do not include java.sql.Driver file in META-INF
> ------------------------------------------------------------
>
> Key: JENA-646
> URL: https://issues.apache.org/jira/browse/JENA-646
> Project: Apache Jena
> Issue Type: Bug
> Components: JDBC
> Affects Versions: Jena 2.11.1
> Reporter: Rob Vesse
> Assignee: Rob Vesse
>
> The JDBC drivers do not currently contain the java.sql.Driver file in
> META-INF as described at
> http://docs.oracle.com/javase/7/docs/api/java/sql/DriverManager.html
> This means that some newer applications that assume the service provider
> mechanisms are used may not automatically recognise the Jena JDBC drivers, an
> example of this appears to be
> http://stackoverflow.com/questions/21963493/play-framework-2-configuration-for-apache-jena-tdb
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
