war file are not getting refreshed using karaf features

I am using karaf features to install a set of related bundles into karaf . The feature has normal bundles and 1 war bundle, and the definition of the feature is as below. RNA_Core RNA_Refnet_Proxy mvn:org.json/json/20160212

Re: Component configuration pid

> On Sep 9, 2016, at 8:07 PM, Benson Margulies wrote: > > > > On Fri, Sep 9, 2016 at 10:00 PM, David Jencks > wrote: > Well, either > 1. you didn’t actually succeed in creating a bundle with a different pid

Re: Component configuration pid

On Fri, Sep 9, 2016 at 10:00 PM, David Jencks wrote: > Well, either > 1. you didn’t actually succeed in creating a bundle with a different pid > for your component. Look in the (I hope generated) xml configuration in > the bundle you’ve created and see if it’s what you

Re: Component configuration pid

Well, either 1. you didn’t actually succeed in creating a bundle with a different pid for your component. Look in the (I hope generated) xml configuration in the bundle you’ve created and see if it’s what you expect. 2. you didn’t actually succeed in deploying your updated bundle. If your new

Re: Hot deploy priority on first start up?

I've confirmed that featuresBootAsynchronous=false felix.fileinstall.active.level = 80 are indeed the settings that are being used. Oddly enough when I ran it again I couldn't reproduce the error on my build environment. However when I set up the same deployment method in a Docker container,

Re: Hot deploy priority on first start up?

If you use the following, it should work * featuresBootAsynchronous=false in etc/org.apache.karaf.features.cfg * felix.fileinstall.active.level = 80 in etc/ org.apache.felix.fileinstall-deploy.cfg If that's not the case, it may be a bug in file install. You need to try verifying if the

Re: features.xml and classpath URL handler

You need to use a prerequisite feature in order to make sure the feature containing the class path url handler is fully handled and started before installing the remaining stuff that actually need to use this url handler. ... mvn:org.ops4j.pax.url/pax-url-classpath/2.4.3 pax-url-handler

Hot deploy priority on first start up?

Hi there, I'm with a group that provisions our own instance of Karaf. We've run into an issue that might be a bug, so I wanted to ask here first. It has to do with a *first-time deployment and start-up* of the Karaf container. We un-tar the instance but before starting it we put our application

Re: features.xml and classpath URL handler

Hi Alex, You have to install pax-url-classpath bundle to have the classpath URL handler. On the other hand, now (since Karaf 4.0.5), both and creates a cfg file in the etc folder. Regards JB On 09/09/2016 06:04 PM, Alex Soto wrote: I guess it is not loaded by default. Added this to my

Re: features.xml and classpath URL handler

I'm not sure the classpath URL handler is loaded. If you do bundle:install classpath: do you have any issue ? Regards JB On 09/09/2016 04:27 PM, Alex Soto wrote: No, I am not using blueprint (at least in this context), this is a URL in the features.xml file. I am trying to deploy a

Re: features.xml and classpath URL handler

No, I am not using blueprint (at least in this context), this is a URL in the features.xml file. I am trying to deploy a default config file as part of my feature. Karaf documentation does not mention all possible URLs it supports. It says: "The file URL is any URL supported by Apache Karaf

Re: features.xml and classpath URL handler

Hi, classpath is not a regular URL: AFAIK, classpath: is a specific Spring URL (not a blueprint regular URL). Do you use the blueprint spring extender ? Regards JB On 09/09/2016 03:42 PM, Alex Soto wrote: Hello, I am trying to deploy a config file which is a resource of one of the

features.xml and classpath URL handler

Hello, I am trying to deploy a config file which is a resource of one of the deployed bundles. I write the features.xml classpath://my :: bundle/my.config.cfg When I run integration tests (PAX-EXAM) I get this error: Error installing boot features java.net.MalformedURLException:

Re: Aw: Re: Problems with 4.1.0-SNAPSHOT

Thanks for the update Jens. It sounds like a wrapper/jline issue. Can you create a Jira about that please ? Thanks, Regards JB On 09/09/2016 10:59 AM, Jens Offenbach wrote: Thanks for your hint... I made a quick fix to continue working with 4.1.0-SNAPSHOT, but I am confronted with a new

Aw: Re: Problems with 4.1.0-SNAPSHOT

Thanks for your hint... I made a quick fix to continue working with 4.1.0-SNAPSHOT, but I am confronted with a new issue: /opt/apache-karaf/bin/shell wrapper:install Exception in thread "main" java.lang.ClassNotFoundException: org.jledit.ConcreteEditorFactory at