I have done some tests. The problem is indeed the coordinator bundle.
Normally there should be an error message when installing the
transaction feature as transaction.blueprint needs the coordinator. I
think this is a bug in the feature service. Probably this is the reason
that I did not spot the problem. I only installed jpa/1.0.4 but did not
fully test it.
There is a simple workaround though.
Just install the coordinator bundle by hand or in your app feature:
install -s mvn:org.apache.felix/org.apache.felix.coordinator/1.0.0
Then the transaction.blueprint comes up.
Christian
On 17.09.2015 09:12, jochenw wrote:
Slightly different aspect (don't know whether I should open a new thread, but
it is related to this one): with Karaf 4.0.1, I tried to use JPA 1.0.4
instead of 2.1.0 - to start with, since switching to annotations will take
some time.
However, the transaction feature 1.3.0 seems not to work with JPA 1.0.4. The
org.apache.aries.transaction.blueprint bundle is just not installed
(although the aries-blueprint feature is installed), and when installing and
starting it manually, it cannot find org.osgi.service.coordinator -
org.apache.felix.coordinator is not part of the JPA 1.0.4 feature. The old
transation 1.1.1 is no longer provided with Karaf 4.0.1, at least not with
the standard distribution.
Of course I have a workaround by building a custom distribution with an
adapted enterprise feature file. It would just be convenient if one could
simply use the 1.x versions of JPA and JTA with standard Karaf, if the
"disruptive" concept stays as it is, it would make switching to Karaf 4.0.1
simpler.
Best Regards,
Jochen
--
View this message in context:
http://karaf.922171.n3.nabble.com/Bundle-is-waiting-for-namespace-handlers-http-aries-apache-org-xmlns-jpa-v1-0-0-tp4042275p4042641.html
Sent from the Karaf - User mailing list archive at Nabble.com.
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
http://www.talend.com
