You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@karaf.apache.org by Charles Moulliard <cm...@gmail.com> on 2011/01/24 13:19:45 UTC
Info about kar archive of Apache Karaf
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
Re: Info about kar archive of Apache Karaf
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Not sure of that :)
It depends what we stand for feature update.
I'm working on ACE around Karaf feature update and lifecycle. I think
that we need to dig on that, feel free to complete the brainstorming
wiki page :)
Regards
JB
On 01/26/2011 05:02 PM, Charles Moulliard wrote:
> Here is my two pence (deux centimes in French) idea.
> If we provide a new KAR archive containing bundles already installed,
> then we should update automatically bundles no matter what is the
> version number of the bundle. This philosophy is similar to what we
> have when deploying WAR or EAR projects
>
>
> On Wed, Jan 26, 2011 at 3:30 PM, Adrian Trenaman<tr...@progress.com> wrote:
>> Hmmmm.
>>
>> If you deploy a new KAR, then the existing bundles *shouldn't* be updated if
>> they're already deployed, IMHO. They should only be deployed if they are a
>> new version of the bundle. Am thinking that in production, bundles with the
>> same version should be identical, no? We shouldn't allow sneaky updates
>> under the version number - or should we?!
>>
>> On 26/01/2011 14:27, Charles Moulliard wrote:
>>>
>>> The missing piece that we have concern updating mechanism if I provide
>>> a new KAR archive, the already deployed bundles will not be updated. I
>>> think that this is possible right now with EBA archive.
>>>
>>> On Wed, Jan 26, 2011 at 2:57 PM, Adrian Trenaman
>>> <ad...@googlemail.com> wrote:
>>>>
>>>> Answers inline!
>>>>
>>>> On 26/01/2011 13:51, Charles Moulliard wrote:
>>>>>
>>>>> ok.
>>>>>
>>>>> So what do you put in the KAR archive, all the bundles required by
>>>>> your project + features describing your project bundles to be deployed
>>>>> and their<features> dependencies with by example camel-jms,
>>>>> hibernate, mysql-driver, ... ?
>>>>
>>>> Yup! Your application, and all of it's bundle dependencies, can be
>>>> packaged
>>>> into the KAR.
>>>>>
>>>>> Do we have a maven plugin to generate the KAR archive like we have
>>>>> with Aries EBA ?
>>>>>
>>>> I have a JIRA open to make a nice maven plugin to do this - for now
>>>> though,
>>>> we have to live with using a selection of existing Maven plugins to
>>>> achieve
>>>> our goal - much as how we currently package Karaf / ServiceMix using the
>>>> features file to pull down all the dependencies for the system/ folder
>>>> before Zipping them up as either .tar.gz or .zip.
>>>>>
>>>>> On Wed, Jan 26, 2011 at 2:08 PM, Adrian Trenaman
>>>>> <ad...@googlemail.com> wrote:
>>>>>>
>>>>>> Hi Charles!
>>>>>>
>>>>>> The Karaf file *does* include bundles - it's really a collection of
>>>>>> features
>>>>>> descriptors and bundles that can be deployed together easily.
>>>>>>
>>>>>> I think the idea will be to pursue a standards based approach (perhaps
>>>>>> based
>>>>>> on Aries EBA and Karaf features) in the future!
>>>>>>
>>>>>> Best,
>>>>>> Ade.
>>>>>>
>>>>>> On 26/01/2011 12:41, Charles Moulliard wrote:
>>>>>>>
>>>>>>> Hi Ade,
>>>>>>>
>>>>>>> From what I read in the next post of my email, kar only includes
>>>>>>> features xml file(s) and no bundles. To deploy an archive containing
>>>>>>> bundles we should use eba archive of project Aries.
>>>>>>>
>>>>>>> Regards,
>>>>>>>
>>>>>>> Charles
>>>>>>>
>>>>>>> On Mon, Jan 24, 2011 at 3:02 PM, Adrian Trenaman
>>>>>>> <ad...@googlemail.com> 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<cm...@gmail.com> 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
>>>>>>>>>
>>
Re: Info about kar archive of Apache Karaf
Posted by Charles Moulliard <cm...@gmail.com>.
Here is my two pence (deux centimes in French) idea.
If we provide a new KAR archive containing bundles already installed,
then we should update automatically bundles no matter what is the
version number of the bundle. This philosophy is similar to what we
have when deploying WAR or EAR projects
On Wed, Jan 26, 2011 at 3:30 PM, Adrian Trenaman <tr...@progress.com> wrote:
> Hmmmm.
>
> If you deploy a new KAR, then the existing bundles *shouldn't* be updated if
> they're already deployed, IMHO. They should only be deployed if they are a
> new version of the bundle. Am thinking that in production, bundles with the
> same version should be identical, no? We shouldn't allow sneaky updates
> under the version number - or should we?!
>
> On 26/01/2011 14:27, Charles Moulliard wrote:
>>
>> The missing piece that we have concern updating mechanism if I provide
>> a new KAR archive, the already deployed bundles will not be updated. I
>> think that this is possible right now with EBA archive.
>>
>> On Wed, Jan 26, 2011 at 2:57 PM, Adrian Trenaman
>> <ad...@googlemail.com> wrote:
>>>
>>> Answers inline!
>>>
>>> On 26/01/2011 13:51, Charles Moulliard wrote:
>>>>
>>>> ok.
>>>>
>>>> So what do you put in the KAR archive, all the bundles required by
>>>> your project + features describing your project bundles to be deployed
>>>> and their<features> dependencies with by example camel-jms,
>>>> hibernate, mysql-driver, ... ?
>>>
>>> Yup! Your application, and all of it's bundle dependencies, can be
>>> packaged
>>> into the KAR.
>>>>
>>>> Do we have a maven plugin to generate the KAR archive like we have
>>>> with Aries EBA ?
>>>>
>>> I have a JIRA open to make a nice maven plugin to do this - for now
>>> though,
>>> we have to live with using a selection of existing Maven plugins to
>>> achieve
>>> our goal - much as how we currently package Karaf / ServiceMix using the
>>> features file to pull down all the dependencies for the system/ folder
>>> before Zipping them up as either .tar.gz or .zip.
>>>>
>>>> On Wed, Jan 26, 2011 at 2:08 PM, Adrian Trenaman
>>>> <ad...@googlemail.com> wrote:
>>>>>
>>>>> Hi Charles!
>>>>>
>>>>> The Karaf file *does* include bundles - it's really a collection of
>>>>> features
>>>>> descriptors and bundles that can be deployed together easily.
>>>>>
>>>>> I think the idea will be to pursue a standards based approach (perhaps
>>>>> based
>>>>> on Aries EBA and Karaf features) in the future!
>>>>>
>>>>> Best,
>>>>> Ade.
>>>>>
>>>>> On 26/01/2011 12:41, Charles Moulliard wrote:
>>>>>>
>>>>>> Hi Ade,
>>>>>>
>>>>>> From what I read in the next post of my email, kar only includes
>>>>>> features xml file(s) and no bundles. To deploy an archive containing
>>>>>> bundles we should use eba archive of project Aries.
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>> Charles
>>>>>>
>>>>>> On Mon, Jan 24, 2011 at 3:02 PM, Adrian Trenaman
>>>>>> <ad...@googlemail.com> 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<cm...@gmail.com> 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
>>>>>>>>
>
Re: Info about kar archive of Apache Karaf
Posted by Adrian Trenaman <tr...@progress.com>.
Hmmmm.
If you deploy a new KAR, then the existing bundles *shouldn't* be
updated if they're already deployed, IMHO. They should only be deployed
if they are a new version of the bundle. Am thinking that in production,
bundles with the same version should be identical, no? We shouldn't
allow sneaky updates under the version number - or should we?!
On 26/01/2011 14:27, Charles Moulliard wrote:
> The missing piece that we have concern updating mechanism if I provide
> a new KAR archive, the already deployed bundles will not be updated. I
> think that this is possible right now with EBA archive.
>
> On Wed, Jan 26, 2011 at 2:57 PM, Adrian Trenaman
> <ad...@googlemail.com> wrote:
>> Answers inline!
>>
>> On 26/01/2011 13:51, Charles Moulliard wrote:
>>> ok.
>>>
>>> So what do you put in the KAR archive, all the bundles required by
>>> your project + features describing your project bundles to be deployed
>>> and their<features> dependencies with by example camel-jms,
>>> hibernate, mysql-driver, ... ?
>> Yup! Your application, and all of it's bundle dependencies, can be packaged
>> into the KAR.
>>> Do we have a maven plugin to generate the KAR archive like we have
>>> with Aries EBA ?
>>>
>> I have a JIRA open to make a nice maven plugin to do this - for now though,
>> we have to live with using a selection of existing Maven plugins to achieve
>> our goal - much as how we currently package Karaf / ServiceMix using the
>> features file to pull down all the dependencies for the system/ folder
>> before Zipping them up as either .tar.gz or .zip.
>>> On Wed, Jan 26, 2011 at 2:08 PM, Adrian Trenaman
>>> <ad...@googlemail.com> wrote:
>>>> Hi Charles!
>>>>
>>>> The Karaf file *does* include bundles - it's really a collection of
>>>> features
>>>> descriptors and bundles that can be deployed together easily.
>>>>
>>>> I think the idea will be to pursue a standards based approach (perhaps
>>>> based
>>>> on Aries EBA and Karaf features) in the future!
>>>>
>>>> Best,
>>>> Ade.
>>>>
>>>> On 26/01/2011 12:41, Charles Moulliard wrote:
>>>>> Hi Ade,
>>>>>
>>>>> From what I read in the next post of my email, kar only includes
>>>>> features xml file(s) and no bundles. To deploy an archive containing
>>>>> bundles we should use eba archive of project Aries.
>>>>>
>>>>> Regards,
>>>>>
>>>>> Charles
>>>>>
>>>>> On Mon, Jan 24, 2011 at 3:02 PM, Adrian Trenaman
>>>>> <ad...@googlemail.com> 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<cm...@gmail.com> 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
>>>>>>>
Re: Info about kar archive of Apache Karaf
Posted by Charles Moulliard <cm...@gmail.com>.
The missing piece that we have concern updating mechanism if I provide
a new KAR archive, the already deployed bundles will not be updated. I
think that this is possible right now with EBA archive.
On Wed, Jan 26, 2011 at 2:57 PM, Adrian Trenaman
<ad...@googlemail.com> wrote:
> Answers inline!
>
> On 26/01/2011 13:51, Charles Moulliard wrote:
>>
>> ok.
>>
>> So what do you put in the KAR archive, all the bundles required by
>> your project + features describing your project bundles to be deployed
>> and their<features> dependencies with by example camel-jms,
>> hibernate, mysql-driver, ... ?
>
> Yup! Your application, and all of it's bundle dependencies, can be packaged
> into the KAR.
>>
>> Do we have a maven plugin to generate the KAR archive like we have
>> with Aries EBA ?
>>
> I have a JIRA open to make a nice maven plugin to do this - for now though,
> we have to live with using a selection of existing Maven plugins to achieve
> our goal - much as how we currently package Karaf / ServiceMix using the
> features file to pull down all the dependencies for the system/ folder
> before Zipping them up as either .tar.gz or .zip.
>>
>> On Wed, Jan 26, 2011 at 2:08 PM, Adrian Trenaman
>> <ad...@googlemail.com> wrote:
>>>
>>> Hi Charles!
>>>
>>> The Karaf file *does* include bundles - it's really a collection of
>>> features
>>> descriptors and bundles that can be deployed together easily.
>>>
>>> I think the idea will be to pursue a standards based approach (perhaps
>>> based
>>> on Aries EBA and Karaf features) in the future!
>>>
>>> Best,
>>> Ade.
>>>
>>> On 26/01/2011 12:41, Charles Moulliard wrote:
>>>>
>>>> Hi Ade,
>>>>
>>>> From what I read in the next post of my email, kar only includes
>>>> features xml file(s) and no bundles. To deploy an archive containing
>>>> bundles we should use eba archive of project Aries.
>>>>
>>>> Regards,
>>>>
>>>> Charles
>>>>
>>>> On Mon, Jan 24, 2011 at 3:02 PM, Adrian Trenaman
>>>> <ad...@googlemail.com> 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<cm...@gmail.com> 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
>>>>>>
>
Re: Info about kar archive of Apache Karaf
Posted by Adrian Trenaman <tr...@progress.com>.
Nice one JB!
On 26/01/2011 14:06, Jean-Baptiste Onofré wrote:
> Hi guys,
>
> regarding the maven plugin, I'm gonna refactore the existing plugins to
> create a generic karaf one and extend goal.
>
> I should be able to work on that on saturday.
>
> Regards
> JB
>
> On 01/26/2011 02:57 PM, Adrian Trenaman wrote:
>> Answers inline!
>>
>> On 26/01/2011 13:51, Charles Moulliard wrote:
>>> ok.
>>>
>>> So what do you put in the KAR archive, all the bundles required by
>>> your project + features describing your project bundles to be deployed
>>> and their<features> dependencies with by example camel-jms,
>>> hibernate, mysql-driver, ... ?
>> Yup! Your application, and all of it's bundle dependencies, can be
>> packaged into the KAR.
>>> Do we have a maven plugin to generate the KAR archive like we have
>>> with Aries EBA ?
>>>
>> I have a JIRA open to make a nice maven plugin to do this - for now
>> though, we have to live with using a selection of existing Maven plugins
>> to achieve our goal - much as how we currently package Karaf /
>> ServiceMix using the features file to pull down all the dependencies for
>> the system/ folder before Zipping them up as either .tar.gz or .zip.
>>> On Wed, Jan 26, 2011 at 2:08 PM, Adrian Trenaman
>>> <ad...@googlemail.com> wrote:
>>>> Hi Charles!
>>>>
>>>> The Karaf file *does* include bundles - it's really a collection of
>>>> features
>>>> descriptors and bundles that can be deployed together easily.
>>>>
>>>> I think the idea will be to pursue a standards based approach
>>>> (perhaps based
>>>> on Aries EBA and Karaf features) in the future!
>>>>
>>>> Best,
>>>> Ade.
>>>>
>>>> On 26/01/2011 12:41, Charles Moulliard wrote:
>>>>> Hi Ade,
>>>>>
>>>>> From what I read in the next post of my email, kar only includes
>>>>> features xml file(s) and no bundles. To deploy an archive containing
>>>>> bundles we should use eba archive of project Aries.
>>>>>
>>>>> Regards,
>>>>>
>>>>> Charles
>>>>>
>>>>> On Mon, Jan 24, 2011 at 3:02 PM, Adrian Trenaman
>>>>> <ad...@googlemail.com> 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<cm...@gmail.com> 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
>>>>>>>
Re: Info about kar archive of Apache Karaf
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi guys,
regarding the maven plugin, I'm gonna refactore the existing plugins to
create a generic karaf one and extend goal.
I should be able to work on that on saturday.
Regards
JB
On 01/26/2011 02:57 PM, Adrian Trenaman wrote:
> Answers inline!
>
> On 26/01/2011 13:51, Charles Moulliard wrote:
>> ok.
>>
>> So what do you put in the KAR archive, all the bundles required by
>> your project + features describing your project bundles to be deployed
>> and their<features> dependencies with by example camel-jms,
>> hibernate, mysql-driver, ... ?
> Yup! Your application, and all of it's bundle dependencies, can be
> packaged into the KAR.
>> Do we have a maven plugin to generate the KAR archive like we have
>> with Aries EBA ?
>>
> I have a JIRA open to make a nice maven plugin to do this - for now
> though, we have to live with using a selection of existing Maven plugins
> to achieve our goal - much as how we currently package Karaf /
> ServiceMix using the features file to pull down all the dependencies for
> the system/ folder before Zipping them up as either .tar.gz or .zip.
>>
>> On Wed, Jan 26, 2011 at 2:08 PM, Adrian Trenaman
>> <ad...@googlemail.com> wrote:
>>> Hi Charles!
>>>
>>> The Karaf file *does* include bundles - it's really a collection of
>>> features
>>> descriptors and bundles that can be deployed together easily.
>>>
>>> I think the idea will be to pursue a standards based approach
>>> (perhaps based
>>> on Aries EBA and Karaf features) in the future!
>>>
>>> Best,
>>> Ade.
>>>
>>> On 26/01/2011 12:41, Charles Moulliard wrote:
>>>> Hi Ade,
>>>>
>>>> From what I read in the next post of my email, kar only includes
>>>> features xml file(s) and no bundles. To deploy an archive containing
>>>> bundles we should use eba archive of project Aries.
>>>>
>>>> Regards,
>>>>
>>>> Charles
>>>>
>>>> On Mon, Jan 24, 2011 at 3:02 PM, Adrian Trenaman
>>>> <ad...@googlemail.com> 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<cm...@gmail.com> 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
>>>>>>
Re: Info about kar archive of Apache Karaf
Posted by Adrian Trenaman <ad...@googlemail.com>.
Answers inline!
On 26/01/2011 13:51, Charles Moulliard wrote:
> ok.
>
> So what do you put in the KAR archive, all the bundles required by
> your project + features describing your project bundles to be deployed
> and their<features> dependencies with by example camel-jms,
> hibernate, mysql-driver, ... ?
Yup! Your application, and all of it's bundle dependencies, can be
packaged into the KAR.
> Do we have a maven plugin to generate the KAR archive like we have
> with Aries EBA ?
>
I have a JIRA open to make a nice maven plugin to do this - for now
though, we have to live with using a selection of existing Maven plugins
to achieve our goal - much as how we currently package Karaf /
ServiceMix using the features file to pull down all the dependencies for
the system/ folder before Zipping them up as either .tar.gz or .zip.
>
> On Wed, Jan 26, 2011 at 2:08 PM, Adrian Trenaman
> <ad...@googlemail.com> wrote:
>> Hi Charles!
>>
>> The Karaf file *does* include bundles - it's really a collection of features
>> descriptors and bundles that can be deployed together easily.
>>
>> I think the idea will be to pursue a standards based approach (perhaps based
>> on Aries EBA and Karaf features) in the future!
>>
>> Best,
>> Ade.
>>
>> On 26/01/2011 12:41, Charles Moulliard wrote:
>>> Hi Ade,
>>>
>>> From what I read in the next post of my email, kar only includes
>>> features xml file(s) and no bundles. To deploy an archive containing
>>> bundles we should use eba archive of project Aries.
>>>
>>> Regards,
>>>
>>> Charles
>>>
>>> On Mon, Jan 24, 2011 at 3:02 PM, Adrian Trenaman
>>> <ad...@googlemail.com> 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<cm...@gmail.com> 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
>>>>>
Re: Info about kar archive of Apache Karaf
Posted by Charles Moulliard <cm...@gmail.com>.
ok.
So what do you put in the KAR archive, all the bundles required by
your project + features describing your project bundles to be deployed
and their <features> dependencies with by example camel-jms,
hibernate, mysql-driver, ... ?
Do we have a maven plugin to generate the KAR archive like we have
with Aries EBA ?
On Wed, Jan 26, 2011 at 2:08 PM, Adrian Trenaman
<ad...@googlemail.com> wrote:
> Hi Charles!
>
> The Karaf file *does* include bundles - it's really a collection of features
> descriptors and bundles that can be deployed together easily.
>
> I think the idea will be to pursue a standards based approach (perhaps based
> on Aries EBA and Karaf features) in the future!
>
> Best,
> Ade.
>
> On 26/01/2011 12:41, Charles Moulliard wrote:
>>
>> Hi Ade,
>>
>> From what I read in the next post of my email, kar only includes
>> features xml file(s) and no bundles. To deploy an archive containing
>> bundles we should use eba archive of project Aries.
>>
>> Regards,
>>
>> Charles
>>
>> On Mon, Jan 24, 2011 at 3:02 PM, Adrian Trenaman
>> <ad...@googlemail.com> 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<cm...@gmail.com> 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
>>>>
>
Re: Info about kar archive of Apache Karaf
Posted by Adrian Trenaman <ad...@googlemail.com>.
Hi Charles!
The Karaf file *does* include bundles - it's really a collection of
features descriptors and bundles that can be deployed together easily.
I think the idea will be to pursue a standards based approach (perhaps
based on Aries EBA and Karaf features) in the future!
Best,
Ade.
On 26/01/2011 12:41, Charles Moulliard wrote:
> Hi Ade,
>
> From what I read in the next post of my email, kar only includes
> features xml file(s) and no bundles. To deploy an archive containing
> bundles we should use eba archive of project Aries.
>
> Regards,
>
> Charles
>
> On Mon, Jan 24, 2011 at 3:02 PM, Adrian Trenaman
> <ad...@googlemail.com> 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<cm...@gmail.com> 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
>>>
Re: Info about kar archive of Apache Karaf
Posted by Charles Moulliard <cm...@gmail.com>.
Hi Ade,
>From what I read in the next post of my email, kar only includes
features xml file(s) and no bundles. To deploy an archive containing
bundles we should use eba archive of project Aries.
Regards,
Charles
On Mon, Jan 24, 2011 at 3:02 PM, Adrian Trenaman
<ad...@googlemail.com> 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 <cm...@gmail.com> 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
>>
>
Re: Info about kar archive of Apache Karaf
Posted by David Jencks <da...@yahoo.com>.
Hi Karafman,
Most of this stuff is implemented and more or less working on my github fork which I think can be accessed through https://github.com/djencks/karaf/tree/feature for browsing or checking out
git clone https://github.com/djencks/karaf.git
cd karaf
git checkout feature
There's a "starter" kar under features/assembly/framework and a sample assembly under assemblies/apache-karaf. My test project that actually installs a useful kar is at https://svn.apache.org/repos/asf/geronimo/sandbox/djencks/txmanager which shows building a kar and a server assembly.
I think it would be great to get more points of view on how this should work. I know I'm strongly biased by my experience with geronimo and idee fixe that all deployment should be done by assembling a new server :-)
Also check out the Possible feature features thread :-)
thanks
david jencks
On Jan 25, 2011, at 3:14 PM, karafman wrote:
>
> I like this functionality. We've been looking for a deployment solution for
> our app for about 6 months, we just haven't gotten our application to the
> point where we were heavily concerned with deployment to think really hard
> about it.
>
> Is there currently a ticket open for this, or does the functionality already
> exist?
>
> -----
> Karafman
> Slayer of the JEE
> Pounder of the Perl Programmer
>
> --
> View this message in context: http://karaf.922171.n3.nabble.com/Re-Info-about-kar-archive-of-Apache-Karaf-tp2332423p2335065.html
> Sent from the Karaf - Dev mailing list archive at Nabble.com.
Re: Info about kar archive of Apache Karaf
Posted by karafman <mv...@comcast.net>.
I like this functionality. We've been looking for a deployment solution for
our app for about 6 months, we just haven't gotten our application to the
point where we were heavily concerned with deployment to think really hard
about it.
Is there currently a ticket open for this, or does the functionality already
exist?
-----
Karafman
Slayer of the JEE
Pounder of the Perl Programmer
--
View this message in context: http://karaf.922171.n3.nabble.com/Re-Info-about-kar-archive-of-Apache-Karaf-tp2332423p2335065.html
Sent from the Karaf - Dev mailing list archive at Nabble.com.
Re: Info about kar archive of Apache Karaf
Posted by David Jencks <da...@yahoo.com>.
(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 <gn...@gmail.com> 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 <cm...@gmail.com> wrote:
>>> Is it similar to eba archive of Aries ?
>>>
>>>
>>> On Mon, Jan 24, 2011 at 3:02 PM, Adrian Trenaman
>>> <ad...@googlemail.com> 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 <cm...@gmail.com> 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
>>
Re: Info about kar archive of Apache Karaf
Posted by Andreas Pieber <an...@gmail.com>.
On Tue, Jan 25, 2011 at 6:01 PM, Charles Moulliard <cm...@gmail.com> wrote:
> So the kar will contain a xml features file and during the deployment
> process deploy all the features defined in the file ?
Yes, all the feature xml files in the kar (zip) 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 ?
It is exactly like if you copy a number of .jar files into the "local"
system repo of karaf, and add the features.xml by using
features:addurl
> Will it be possible to update the kar archive and so update bundles defined in the features list ?
By the moment indirectly; again: it's similar as if you unpack a new
version: all packages with the same version (name) are overwritten;
those with a different version added in addition. Features.xml in a
new version will be added again letting you to update --> no automatic
update here by the moment
kind regards,
andreas
>
> On Mon, Jan 24, 2011 at 4:53 PM, Guillaume Nodet <gn...@gmail.com> 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 <cm...@gmail.com> wrote:
>>> Is it similar to eba archive of Aries ?
>>>
>>>
>>> On Mon, Jan 24, 2011 at 3:02 PM, Adrian Trenaman
>>> <ad...@googlemail.com> 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 <cm...@gmail.com> 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
>>
>
Re: Info about kar archive of Apache Karaf
Posted by Charles Moulliard <cm...@gmail.com>.
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 <gn...@gmail.com> 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 <cm...@gmail.com> wrote:
>> Is it similar to eba archive of Aries ?
>>
>>
>> On Mon, Jan 24, 2011 at 3:02 PM, Adrian Trenaman
>> <ad...@googlemail.com> 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 <cm...@gmail.com> 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
>
Re: Info about kar archive of Apache Karaf
Posted by Guillaume Nodet <gn...@gmail.com>.
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 <cm...@gmail.com> wrote:
> Is it similar to eba archive of Aries ?
>
>
> On Mon, Jan 24, 2011 at 3:02 PM, Adrian Trenaman
> <ad...@googlemail.com> 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 <cm...@gmail.com> 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
Re: Info about kar archive of Apache Karaf
Posted by Charles Moulliard <cm...@gmail.com>.
Is it similar to eba archive of Aries ?
On Mon, Jan 24, 2011 at 3:02 PM, Adrian Trenaman
<ad...@googlemail.com> 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 <cm...@gmail.com> 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
>>
>
Re: Info about kar archive of Apache Karaf
Posted by Adrian Trenaman <ad...@googlemail.com>.
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 <cm...@gmail.com> 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
>