[KARAF-3976] Broken compatibility with 3.x jdbc DataSources

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 4.0.1
• Fix Version/s: 4.0.11, 4.1.4, 4.2.0.M2
• Component/s: karaf
• Assignee: Jean-Baptiste Onofré
• Reporter: Sergey
• Created: 07/Sep/15 10:44
• Updated: 15/Sep/18 05:03
• Resolved: 15/Dec/17 09:49

Description

1st of all, current documentaion is wrong, because command names was changed to jdbc:ds-info, for example, but http://karaf.apache.org/manual/latest/users-guide/jdbc.html still contains jdbc:info command names.

Most important compatibility breaking change was another one: in karaf 3.x I was able to deploy DataSource using spring-dm xml or blueprint, and it was registered as a service and in jndi, and was listed using jdbc:datasources command. Right now no datasources are listed.

karaf@root()> jndi:names
JNDI Name                                 | Class Name
------------------------------------------------------------------------------------------
osgi:service/jdbc/zeusDataSource          | net.sourceforge.jtds.jdbcx.JtdsDataSource
osgi:service/jdbc/arenaDS                 | net.sourceforge.jtds.jdbcx.JtdsDataSource
osgi:service/jdbc/tomsDS                  | net.sourceforge.jtds.jdbcx.JtdsDataSource
osgi:service/jdbc/cofDS                   | com.sybase.jdbc3.jdbc.SybDataSource
osgi:service/jdbc/fidbDataSource          | net.sourceforge.jtds.jdbcx.JtdsDataSource
osgi:service/jdbc/murexDS                 | com.sybase.jdbc3.jdbc.SybDataSource
osgi:service/jdbc/gpDataSource            | org.postgresql.ds.PGPoolingDataSource

karaf@root()> jdbc:ds-info jdbc/fidbDataSource
Property       | Value
---------------------------------------------------------------------
driver.version | 1.2.2
db.version     | 10.50.4000
db.product     | Microsoft SQL Server
url            | jdbc:jtds:sqlserver:
driver.name    | jTDS Type 4 JDBC Driver for MS SQL Server and Sybase
username       | ...

karaf@root()> jdbc:ds-list
Name | Product | Version | URL | Status
---------------------------------------

Issue Links

• links to: GitHub Pull Request #431