Derby is looking for assistance with OSGi compatibility

[Mark Raynsford]

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.

--
Mark Raynsford | http://www.io7m.com

[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

[Christoph Läubrich]

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é:

[Jean-Baptiste Onofré]

Hi,

I agree, my point is that we can help anyway directly in the project.
Pax JDBC is more a workaround at driver level.

Regards
JB

[Mark Raynsford]

On 2019-10-18T07:02:55 +0200

'Christoph Läubrich' via OPS4J <op...@googlegroups.com> wrote:

> 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?

Thanks, all!

Yes, I'm going to get the OSGi headers into the published Derby
artifacts (at a minimum) this weekend. Implementing the OSGi JDBC
service also looks pretty easy, so I'll be attempting that too.

[Jean-Baptiste Onofré]

Nice !

Don't hesitate to ping if needed !

Regards
JB

[Steinar Bang]

>>>>> "'Mark Raynsford' via OPS4J" <ops4j-/JYPxA39Uh5...@public.gmane.org>:

> Yes, I'm going to get the OSGi headers into the published Derby
> artifacts (at a minimum) this weekend. Implementing the OSGi JDBC
> service also looks pretty easy, so I'll be attempting that too.

Another nice thing to have for us karaf users, is if the JDBC service
has a karaf feature it can be loaded and activated with.

For reference: Here's my issue and PR to the PostgreSQL JDBC maintainers
that was accepted into version 42.2.7 of the PostgreSQL JDBC driver:
https://github.com/pgjdbc/pgjdbc/issues/1552
https://github.com/pgjdbc/pgjdbc/pull/1554

(I'm also a derby user. I use in-memory derby from pax-jdbc for test
databases and PostgreSQL for production use. I use liquibase to set up
the schema and initial data for both derby and PostgreSQL)