Bug #107586 Please support the Data Service Specification for JDBC™ Technology
Submitted: 17 Jun 2022 11:51 Modified: 17 Jun 2022 12:37
Reporter: Christoph Läubrich Email Updates:
Status: Verified Impact on me:
Category:Connector / J Severity:S4 (Feature request)
Version:8.0 OS:Any
Assigned to: CPU Architecture:Any

[17 Jun 2022 11:51] Christoph Läubrich
OSGi defines a Data Service Specification for JDBC™ Technology[1] that provides a convenient and save way to obtain DataSources. Even though it can be implemented by clients it is advised that JDBC driver vendors include an implementation if possible for the following reasons:

1) The vendor has the best knowledge how to create and configure the participating objects.
2) Changes in the internal implementation, e.g. refactoring of class names can be reflected an managed easier in the original repository
3) No gap between deployment of new version and connector code
4) For non-osgi users, this is completely transparent and the is no need for them to change, but OSGi users will be happy to not reinvent the wheel, the library can just be dropped inside a framework and seaming less integrate, for example with the JPA Specification[2].
5) No need to export any packages (in the context of OSGi) as consumers do not need to access the internal state.

Because of this I'd like to propose adding an implementation for a DataSourceFactory in this repository and offering to contribute the inital implementation.

[1] https://docs.osgi.org/specification/osgi.cmpn/8.0.0/service.jdbc.html
[2] http://docs.osgi.org/specification/osgi.cmpn/8.0.0/service.jpa.html
[3] https://docs.osgi.org/specification/osgi.cmpn/8.0.0/service.jdbc.html#org.osgi.service.jdb...

How to repeat:
Currently Connector/J do not contains such code, so deployment in OSGi is possible but user must supply additional code.
[17 Jun 2022 12:37] MySQL Verification Team
Hello Christoph,

Thank you for the feature request!