commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ralf Hauser (JIRA)" <>
Subject [jira] Commented: (DBCP-152) [DBCP] add a socketFactory attribute to BasicDataSource (to allow SSL "thread"-safe)
Date Sun, 22 Jul 2007 15:03:06 GMT


Ralf Hauser commented on DBCP-152:


thx for your explanations.

Unfortunately, it appears that "JSR 221: JDBCTM 4.0 API Specification" is final since only
~half a year and I fear that the community process will not be able to quickly pick this up.
Anyway, I drew the attention on the topic by sending mail to and
the listed sun employees.

In the meantime (probably months if not years), I guess it will be the challenge for dbcp
to anticipate an approach with which you can easily support this already now and if the JDBC
standard were to support this, minimize the migration effort for those using it/allow for
easy backward compatibility.
Since most people and vendor's don't require this security yet, how about adding a thin interface
and a default implementation that supports the mysql approach for now and if other vendor's
have different approaches, do both i) add a switch to the default implementation (e.g. on
the driver name) and ii) also provide the option to use an own interface implementation instead
with a simple configuration step?

Rgds Ralf

> [DBCP] add a socketFactory attribute to BasicDataSource (to allow SSL "thread"-safe)
> ------------------------------------------------------------------------------------
>                 Key: DBCP-152
>                 URL:
>             Project: Commons Dbcp
>          Issue Type: Improvement
>    Affects Versions: 1.2
>         Environment: Operating System: All
> Platform: Other
>            Reporter: Ralf Hauser
>            Priority: Minor
>             Fix For: 1.3
> An app that accesses 2 datasources at two different places with different
> security policies via SSL (different set of permitted ciphers) currently is out
> of luck (
> The basic datasource should be enhanced with 
>   String socketFactory = "";
> and the corresponding getter and setter method, etc.
> org.apache.commons.dbcp.DriverConnectionFactory.createConnection() could then
> hand-over this full className via its Properties argument to enable different
> SSL policies per datasource (so, since the application programmer doesn't have
> the thread under her control, I guess it should rather be called "dataSource-safe").
> The jdbc driver implementation can then use this to take the appropriate socket
> factory when creating a connection.
> See also

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message