Hi Gerald, I haven’t tried the derby stuff there by myself but from the context and the examples I would guess that pax-jdbc-derby will give you the option to create a DataSource with a embedded database (which is not accessible externally), whereas pax-jdbc-derbyclient will give you the option to create a DataSource with a connection to a remote derby database. These DataSource services will be registered in the OSGi service registry and can be consumed by other bundles.
AFAIK the current derby drivers are JDBC 4 compliant. Best regards Stephan From: Gerald Kallas <[email protected]> Sent: Tuesday, 22 February 2022 23:55 To: [email protected] Subject: Expose Derby database created inside Karaf Hi all, I did create a Derby database inside Karaf following https://karaf.apache.org/manual/latest/#_datasources_jdbc<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fkaraf.apache.org%2Fmanual%2Flatest%2F%23_datasources_jdbc&data=04%7C01%7Cstephan.siano%40sap.com%7Cecbc5983dbbb41b61dbd08d9f6566bb9%7C42f7676cf455423c82f6dc2d99791af7%7C0%7C0%7C637811673972731606%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=p4anptaa99qIyAwnGW9%2F1yFzoSmxoDPNHWXKkH%2Bvuxc%3D&reserved=0>. Can this database be exposed for external access via host:port? Is the Derby JDBC driver JDBC 4.0 compliant? Thanks for any response Gerald
