This is an area which is not really well supported. The first thing is that features are kinda supposed to be static. We could however support upgrading from one version to another (and also support some kind of SNAPSHOT which would be handy when updating a file in the deploy folder). It could compute the set of bundles that need to be installed and the set of bundles to uninstall and perform the changes. For the configuration, I'm not sure how to handle the changes, as the configuration in the feature is mostly an initial configuration but it could be changed by users afterward, so I'm kinda tempted to say that we would only register new properties and let existing ones as they are. I've raise a JIRA issue for that: https://issues.apache.org/jira/browse/KARAF-129
On Mon, Jul 19, 2010 at 03:51, Mark Derricutt <[email protected]> wrote: > Hi all, > > I was wondering about best practices for updating features in a Karaf > based deployment. > > In our current setup, we have our features XML file dropped into the > ./deploy directory, and the feature ( our app ) loads up fine, > however, if I modify the feature file, either to change a > <configuation/> element, or change a <bundle/> reference, Karaf never > seems to pick up this change. > > At this stage, we're not changing the version number of the feature, > but even when I also did that I didn't see Karaf update the running > bundles. > > Am I missing something simple here? > > Thanks, > Mark > > > > -- > Pull me down under... > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com
