Am I right that Karaf 4 jdbc feature requires now some external
DataSourceFactory libraries (unlike Karaf 3)?

I've installed these features:
jpa                 | 2.0.0            | x        | Started |
enterprise-4.0.0
openjpa             | 2.3.0            | x        | Started |
enterprise-4.0.0
jdbc                | 4.0.0            | x        | Started |
enterprise-4.0.0
pax-jdbc-config     | 0.6.0            | x        | Started |
org.ops4j.pax.jdbc-0.6.0
pax-jdbc-mysql      | 0.6.0            | x        | Started |
org.ops4j.pax.jdbc-0.6.0
pax-jdbc-pool-aries | 0.6.0            | x        | Started |
org.ops4j.pax.jdbc-0.6.0

Then I've created my MySQL datasource:
jdbc:ds-create -dn mysql-pool-xa -url jdbc:mysql://host/dbname -u root -p
admin dbname

ds-factories command output:
Name          | Class                         | Version
-------------------------------------------------------
mysql-pool-xa | com.mysql.jdbc.Driver-pool-xa |
mysql-pool    | com.mysql.jdbc.Driver-pool    |
mysql         | com.mysql.jdbc.Driver         |

Config file is created and it seems to be correct:
dataSourceName="dbname"
osgi.jdbc.driver.name="mysql-pool-xa"
password="admin"
service.factoryPid="org.ops4j.datasource"
service.pid="org.ops4j.datasource.094411fb-f8b6-4794-81d6-5077cc00643a"
url="jdbc:mysql://host/dbname"
user="root"

Then I see doubled datasource. And both of them miss password somehow...
ds-list command output:
Name   | Product | Version | URL | Status
-----------------------------------------------------------------------------------------------------
dbname |         |         |     | Error Access denied for user
''@'192.168.9.6' (using password: NO)
dbname |         |         |     | Error Access denied for user
''@'192.168.9.6' (using password: NO)

Am I right about jdbc commands changes? How to fix my problems with
datasources?



--
View this message in context: 
http://karaf.922171.n3.nabble.com/Karaf-4-jdbc-commands-changes-and-problems-tp4041571.html
Sent from the Karaf - User mailing list archive at Nabble.com.

Reply via email to