I have declared a java.sql.XADataSource as OSGi service. With Aries
auto-enlistment, my bundle automatically also publishes a
java.sql.DataSource:

JBossFuse:admin@mowesb> osgi:ls 92
MOW ESB Datasource (92) provides:
---------------------------------
(...)
aries.xa.name = auditlogxa
datasource.name = auditlogxa
objectClass = [javax.sql.XADataSource]
osgi.service.blueprint.compname = auditDataSourceXA
service.id = 1079
----
aries.managed = true
aries.xa.aware = true
aries.xa.name = auditlogxa
datasource.name = auditlogxa
objectClass = [javax.sql.DataSource]
osgi.service.blueprint.compname = auditDataSourceXA
service.id = 1080
service.ranking = 1000
(...)

When I refer to the XADataSource in another bundle, the  service is found.
<reference id="auditDataSource" interface="javax.sql.XADataSource"
filter="(datasource.name=auditlogxa)" />

When I refer to the DataSource in another bundle, the service isn't:
<reference id="auditDataSource" interface="javax.sql.DataSource"
filter="(datasource.name=auditlogxa)" />

This is the error:
org.osgi.service.resolver.ResolutionException: Unable to resolve root:
missing requirement [root] osgi.identity;
osgi.identity=be.vlaanderen.mow.esb.connector-edelta; type=osgi.bundle;
version="[1.0.0.SNAPSHOT,1.0.0.SNAPSHOT]"; resolution:=mandatory [caused by:
Unable to resolve be.vlaanderen.mow.esb.connector-edelta/1.0.0.SNAPSHOT:
missing requirement [be.vlaanderen.mow.esb.connector-edelta/1.0.0.SNAPSHOT]
osgi.service; effective:=active;
filter:="(objectClass=org.apache.wss4j.dom.validate.Validator)" [caused by:
Unable to resolve be.vlaanderen.mow.esb.generiek-service/1.0.0.SNAPSHOT:
missing requirement [be.vlaanderen.mow.esb.generiek-service/1.0.0.SNAPSHOT]
osgi.service; effective:=active;
filter:="(&(objectClass=javax.sql.DataSource)(datasource.name=auditlogxa))"]]

I really have no clue why the DataSource isn't found...



--
View this message in context: 
http://karaf.922171.n3.nabble.com/Aries-auto-enlistment-DataSource-not-found-tp4042850.html
Sent from the Karaf - User mailing list archive at Nabble.com.

Reply via email to