I already commented there, in a perfect world there would be no need to
have extra libs to use JDBC drivers in OSGi, thats why I add support for
it whenever possible even though it often takes some time (approx 8
month in both cases):
https://github.com/microsoft/mssql-jdbc/pull/700
https://github.com/MariaDB/mariadb-connector-j/pull/133
IMO instead of adding own support we better should convince open-source
projects to add first-class support for osgi/JDBC service, so +1 for the
request from my side. As it seems you have added initial code for derby
(or at least readded it) you might want to contribute the code to
derby-project under required license?
Am 18.10.19 um 06:16 schrieb Jean-Baptiste Onofré:
Hi Mark,
I will take a look on the Jira. As we are working on Pax JDBC, and Derby
is used there (wrapped), we already have good OSGi support in Derby.
Thanks for sharing,
Regards
JB
On 17/10/2019 21:09, 'Mark Raynsford' via OPS4J wrote:
Hello!
I recently posted to the Derby list because I noticed that Derby
10.15.1.3 didn't have any OSGi headers in the manifest. Rick Hillegas
emailed back and has created an issue to track this:
https://issues.apache.org/jira/browse/DERBY-7056
He said: "None of the active Derby contributors is an OSGi expert. We
will need your advice on what's required."
I'm by no means an OSGi expert, although I do have some idea as to what
probably needs to be done, having assisted various other projects with
OSGi compatibility. It occurred to me, however, that I know of a few
people who know OSGi, know JDBC, and know Derby to some extent. :)
I'd appreciate your input on that ticket, if you can spare the time.
--
--
------------------
OPS4J - http://www.ops4j.org - ops4j@googlegroups.com
---
You received this message because you are subscribed to the Google Groups "OPS4J" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to ops4j+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/ops4j/853b21e7-1f9c-2477-346d-e18f846dafd2%40googlemail.com.
