You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
OSGi defines a Data Service Specification for JDBC™ Technology 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:
The vendor has the best knowledge how to create and configure the participating objects.
Changes in the internal implementation, e.g. refactoring of class names can be reflected an managed easier in the original repository
No gap between deployment of new version and connector code
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.
Because of this I'd like to propose adding an implementation for a DataSourceFactory in this repository and provide a PR for this.
You can find a short introduction here: http://docs.osgi.org/specification/osgi.core/8.0.0/framework.module.html#d0e1755
Actually, beside some implementation of a standard java-interface and some extra headers in the manifest nothing will change, so an OSGi-Bundle is still a standard Jar, the only difference is that it could be used in plain java and OSGi without any effort.
OSGi defines a Data Service Specification for JDBC™ Technology 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:
Because of this I'd like to propose adding an implementation for a DataSourceFactory in this repository and provide a PR for this.
FYI @stbischof
The text was updated successfully, but these errors were encountered: