Re: Karaf-4.0.7/8 - ResolutionException for existing Aries TransactionControl Service.

That worked. Thanks again. Erwin > On Dec 30, 2016, at 13:52, Erwin Hogeweg wrote: > > Hi Tim, > > Thanks for your reply. I’ll give that a try. > > Erwin > >> On Dec 30, 2016, at 13:50, Tim Ward > > wrote: >> >> David is right, >> >> there is a bug in the pack

Re: Karaf-4.0.7/8 - ResolutionException for existing Aries TransactionControl Service.

Hi Tim, Thanks for your reply. I’ll give that a try. Erwin > On Dec 30, 2016, at 13:50, Tim Ward wrote: > > David is right, > > there is a bug in the packaging of the Aries local transaction control > service implementation. You should just be able to use the XA implementation > (which als

Re: Karaf-4.0.7/8 - ResolutionException for existing Aries TransactionControl Service.

Hi David, > My guess is that the bundle providing the TransactionControl service doesn’t > say so by having a Provide-Capability header for it. For runtime resolution > the effectice=active requirements don’t matter but for at last subsystem > resolution they do. Thanks for your reply. Looks

Re: Karaf-4.0.7/8 - ResolutionException for existing Aries TransactionControl Service.

David is right, there is a bug in the packaging of the Aries local transaction control service implementation. You should just be able to use the XA implementation (which also supports local transactions) instead, or you can wait for a fix in the snapshots, which will likely appear in the new

Re: Karaf-4.0.7/8 - ResolutionException for existing Aries TransactionControl Service.

My guess is that the bundle providing the TransactionControl service doesn’t say so by having a Provide-Capability header for it. For runtime resolution the effectice=active requirements don’t matter but for at last subsystem resolution they do. david jencks > On Dec 30, 2016, at 6:08 AM, Erw

Karaf-4.0.7/8 - ResolutionException for existing Aries TransactionControl Service.

Hi, I am having problems getting a feature working with the TransactionControl Service under Karaf. The error msg suggests that the service is missing or not active, but I am at a loss of why. This is the error: [caused by: Unable to resolve com.my.persistence.repositories/1.0.0.SNAPSHOT_20161