Scott, That would explain it, so if it's in the enterprise bundle and that repo isn't installed, then it won't be found. I didn't think the enterprise repo was installed by default in the default karaf. I'm using a custom distribution and I definitely don't think it's added, but I'll add it which should resolve the problem. Thanks!
Ryan On Fri, Aug 30, 2019 at 4:30 PM Scott Lewis <sle...@composent.com> wrote: > In my installation of Karaf, the transaction-api is part of enterprise > which comes with enterprise-4.2.6. > > I'm puzzled by why the transaction-api is not available for you, and by > why it wasn't installed as part of the Hazelcast provider install. When I > install in Karaf 4.2.6 (below) it works fine. > > If this remains a problem, I'll put references directly to the > javax.transaction bundles in the Hazelcast provider karaf-features.xml. I > had no idea that this would prove problematic. > > Scott > > karaf@root()> feature:install -v transaction-api > Adding features: transaction-api/[1.2.0,1.2.0] > Changes to perform: > Region: root > Bundles to install: > mvn:javax.el/javax.el-api/3.0.0 > mvn:javax.enterprise/cdi-api/1.2 > mvn:javax.interceptor/javax.interceptor-api/1.2 > mvn:javax.transaction/javax.transaction-api/1.2 > > mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.javax-inject/1_2 > mvn:org.ops4j.pax.transx/pax-transx-tm-api/0.4.3 > Installing bundles: > mvn:javax.el/javax.el-api/3.0.0 > mvn:javax.enterprise/cdi-api/1.2 > mvn:javax.interceptor/javax.interceptor-api/1.2 > mvn:javax.transaction/javax.transaction-api/1.2 > > mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.javax-inject/1_2 > mvn:org.ops4j.pax.transx/pax-transx-tm-api/0.4.3 > Starting bundles: > javax.el-api/3.0.0 > org.apache.servicemix.bundles.javax-inject/1.0.0.2 > javax.interceptor-api/1.2.0 > javax.enterprise.cdi-api/1.2.0 > javax.transaction-api/1.2.0 > org.ops4j.pax.transx.pax-transx-tm-api/0.4.3 > > > > On 8/30/2019 1:08 PM, Ryan Moquin wrote: > > Actually, I guess I don't know where transaction-api comes from since it's > not found if I try to install it. > > On Fri, Aug 30, 2019 at 3:22 PM Ryan Moquin <fragility...@gmail.com> > wrote: > >> I'll just install them manually. >> >> On Fri, Aug 30, 2019, 2:59 PM Ryan Moquin <fragility...@gmail.com> wrote: >> >>> No, they are referenced in the feature as dependencies, I thought it >>> would get installed. >>> >>> On Fri, Aug 30, 2019, 12:17 PM Jean-Baptiste Onofré <j...@nanthrax.net> >>> wrote: >>> >>>> Hi, >>>> >>>> do you have transaction & transaction-api features installed ? >>>> >>>> Regards >>>> JB >>>> >>>> On 30/08/2019 18:06, Ryan Moquin wrote: >>>> > >>>> > when I try to install it, it fails with a missing dependency for some >>>> > reason: >>>> > >>>> > org.apache.felix.resolver.reason.ReasonException: Unable to resolve >>>> > root: missing requirement [root] osgi.identity; >>>> > osgi.identity=ecf-rs-distribution-hazelcast; type=karaf.feature; >>>> > version="[1.4.0,1.4.0]"; >>>> > >>>> filter:="(&(osgi.identity=ecf-rs-distribution-hazelcast)(type=karaf.feature)(version>=1.4.0)(version<=1.4.0))" >>>> > [caused by: Unable to resolve ecf-rs-distribution-hazelcast/1.4.0: >>>> > missing requirement [ecf-rs-distribution-hazelcast/1.4.0] >>>> osgi.identity; >>>> > osgi.identity=transaction-api; type=karaf.feature] >>>> > >>>> > So that's a bummer. >>>> > >>>> > On Thu, Aug 29, 2019 at 5:41 PM Scott Lewis <sle...@composent.com >>>> > <mailto:sle...@composent.com>> wrote: >>>> > >>>> > Hi Ryan, >>>> > >>>> > On 8/29/2019 7:17 AM, Ryan Moquin wrote: >>>> >> It doesn't look like that hazelcast provider is part of the main >>>> >> ecf feature repo for karaf? >>>> > >>>> > Not yet. I will look to add it soon, however. FWIW, it is part >>>> of >>>> > the ECF bndtools workspace [1]. >>>> > >>>> >> Do we need to manually deploy the feature xml for the hazelcast >>>> >> provider to our local maven repo to install it or is it available >>>> >> in a maven repository somewhere? >>>> > >>>> > It is available as a karaf-feature (http jar access) here [2]. >>>> > Feel free to put into local maven repo if you prefer. I am going >>>> > to try to deploy this and some of the other distribution providers >>>> > to maven central as well. >>>> > >>>> > Scott >>>> > >>>> > [1] https://github.com/ECF/bndtools.workspace >>>> > >>>> > [2] >>>> > >>>> https://github.com/ECF/HazelcastProvider/blob/master/build/karaf-features.xml >>>> > >>>> > >>>> >> >>>> >> Ryan >>>> >> >>>> >> On Tue, Aug 6, 2019, 6:17 PM Scott Lewis <sle...@composent.com >>>> >> <mailto:sle...@composent.com>> wrote: >>>> >> >>>> >> <stuff deleted> >>>> >> > One current shortcoming is that the Hazelcast provider does >>>> >> not yet >>>> >> > have a set of Karaf features for it (like most other ECF RS >>>> >> > providers), but that would be easy for us to create/produce >>>> >> if requested. >>>> >> >>>> >> A karaf feature was added [1] for version 1.4.0 of the >>>> Hazelcast >>>> >> distribution provider [2]. >>>> >> >>>> >> Scott >>>> >> >>>> >> [1] >>>> >> >>>> https://github.com/ECF/HazelcastProvider/blob/master/build/karaf-features.xml >>>> >> >>>> >> [2] https://github.com/ECF/HazelcastProvider >>>> >> >>>> >> >>>> >>>> -- >>>> Jean-Baptiste Onofré >>>> jbono...@apache.org >>>> http://blog.nanthrax.net >>>> Talend - http://www.talend.com >>>> >>>
