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
On 18/10/2019 07:02, 'Christoph Läubrich' via OPS4J wrote:
> I already commented there, in a perfect world there would be no need
> to have extra libs to use JDBC
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
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
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
