(moving to dev since this is really discussion about how this stuff should work... I don't think anything is final about this)
So far.... features.xml and .kar files are not bundles. IIUC aries .eba are bundles. I don't know if there's a reason to make a .kar file a bundle. As of yesterday assembling a server using kar files or adding a kar file to an existing karaf instance will install any feature.xml files in the car but not start the features. When assembling the server the feature repo is added to the .cfg for the feature service, whereas adding to a running instance will modify the internally saved feature service state. I think that there should be a maven plugin configuration flag or use of maven dependency scope that determines whether the features listed in the features.xml in the .kar are started. This info would also end up in the feature service .cfg, not the saved state. At the moment I don't know if there is any way to undeploy or redeploy a .kar. I wonder how practical this is. Working with geronimo I _always_ have found it much easier to set up a maven build that assembles the server I'm interested in and just reassemble the server for any change rather than trying to redeploy the just the bits that have changed. I have found that any time lost in the build process is more than made up for in having full documentation of what is in the server I'm working with. However, this seems to be a somewhat unusual point of view. thanks david jencks On Jan 25, 2011, at 9:01 AM, Charles Moulliard wrote: > So the kar will contain a xml features file and during the deployment > process deploy all the features defined in the file ? > What will appear in the list of bundles --> the list of bundles > deployed according to features xml file or the bundle corresponding to > the features file ? Will it be possible to update the kar archive and > so update bundles defined in the features list ? > > On Mon, Jan 24, 2011 at 4:53 PM, Guillaume Nodet <[email protected]> wrote: >> Yes, kars are for features what eba are for aries applications. >> Though David Jencks is currently doing a lot of work in this area to >> have a nice maven integration for kars, so that building a karaf >> distribution will be done done in a very simply way by referencing >> kars as maven dependencies and kars will be created as a maven >> packaging along with features. >> >> On Mon, Jan 24, 2011 at 16:46, Charles Moulliard <[email protected]> >> wrote: >>> Is it similar to eba archive of Aries ? >>> >>> >>> On Mon, Jan 24, 2011 at 3:02 PM, Adrian Trenaman >>> <[email protected]> wrote: >>>> The purpose of the Kar file is to facilitate easy packaging and >>>> deployment of Karaf features. A feature can have its own bundles *and* >>>> all its dependencies placed in a Kar; then, when the Kar archive file >>>> is dropped into a deploy directory, the bundles are extracted to the >>>> local drive in a psuedo-Maven directory structure, and any features >>>> files therein are automatically registered in the runtime. This makes >>>> deployment of Karaf solutions easier, particularly when on production >>>> machines where Maven resolution is not possible. >>>> >>>> On 24/01/2011, Charles Moulliard <[email protected]> wrote: >>>>> Hi, >>>>> >>>>> What is the purpose of the archive kar that we can deploy now on Karaf >>>>> ? Benefits ? >>>>> >>>>> Regards, >>>>> >>>>> Charles Moulliard >>>>> >>>>> Sr. Principal Solution Architect - FuseSource >>>>> Apache Committer >>>>> >>>>> Blog : http://cmoulliard.blogspot.com >>>>> Twitter : http://twitter.com/cmoulliard >>>>> Linkedin : http://www.linkedin.com/in/charlesmoulliard >>>>> Skype: cmoulliard >>>>> >>>> >>> >> >> >> >> -- >> Cheers, >> Guillaume Nodet >> ------------------------ >> Blog: http://gnodet.blogspot.com/ >> ------------------------ >> Open Source SOA >> http://fusesource.com >>
