I am also using in my feature-file with karaf 4.0.7 and when I
install the feature I get 4 equal datasources. So it seems like it is not
completely fixed.
--
View this message in context:
http://karaf.922171.n3.nabble.com/Karaf-4-0-5-jdbc-config-tp4046858p4048504.html
Sent from the Karaf -
Thanx jbonofre.
That's exactly what I was doing (using )
I will wait to version 4.0.6
--
View this message in context:
http://karaf.922171.n3.nabble.com/Karaf-4-0-5-jdbc-config-tp4046858p4046868.html
Sent from the Karaf - User mailing list archive at Nabble.com.
If you use 4.0.5, you may face an issue that I fixed when using
element in the feature.
Now, Karaf automatically creates the cfg file when you use
element. However, we had an issue with ManagedServiceFactory format
(like foo-bar.cfg). It will be fixed in 4.0.6.
Regards
JB
On 06/15/2016
That sounds a bit strange. Maybe you ended up with two configurations that
then create two DataSources.
It could be because the config as ManagedServiceFactory. I think the config
admin support in features is not compatible with it.
Christian
2016-06-15 8:13 GMT+02:00 conejo
I have solved the problem as follows:
1. I am using my own assembly.
2. It seems the problem that I comment occurs if I include the configuration
file datasource in my feature.
3. I removed the file of the feature and I put it directly in the /etc my
distribution.
Everything works.
--
View
I have an installation of karaf 4.0.5.
I create the file etc/org.ops4j.datasource-myDS with the following
information:
url = jdbc:h2:file:./db/myDatabase
dataSourceName = myDS
osgi.jdbc.driver.name = H2-pool-xa
The result is that two javax.sql.DataSource services are created with the
same name =
