You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@karaf.apache.org by Charles Moulliard <cm...@gmail.com> on 2011/02/11 18:15:59 UTC
OpenEJB and Enterprise Features
Hi,
OpenEJB project has created a feature file to deploy their bundles.
This should be an excellent candidate for our Enterprise Features file
and a compagnion for Aries. Is it better to copy / paste their
features in our file or to point to their feature file in
org.apache.karaf.features.cfg ?
+ 1 : to copy/paste = add their file in karaf.features.cfg
- 1 : to copy/paste = add their file in karaf.features.cfg
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: OpenEJB and Enterprise Features
Posted by Charles Moulliard <cm...@gmail.com>.
Hi Guillaume,
There is no ambiguity nor misunderstanding.
If we create a wiki web page containing references with external
projects contributing to OSGI world, this is fine for me. We could
list there the existing features file like servicemix, camel,
activemq, openejb, ... and categorized them according to their purpose
: Integration Web, J2EE, ...
In this page, we can refer to the features section of karaf doc to
explain how to use those features repository with Karaf.
Remark : We could imagine to create a small certification program that
partners can adopt to certify their features repo according to karaf
releases !! Imagine the time that architects/developers can win with
that.
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
On Mon, Feb 14, 2011 at 10:38 AM, Guillaume Nodet <gn...@gmail.com> wrote:
> I think you misunderstood.
> I have always wanted to deploy OpenEJB on ServiceMix Kernel / Karaf
> since ages, but never had the time to work on it, so I do think it's a
> great idea.
> So it's not about OpenEJB, it's about Karaf not being able to bring
> all projects as dependencies. Karaf isn't Geronimo, and I think we
> should try to push the maintenance of those feature descriptors back
> to the corresponding projects (Aries, Camel, CXF, OpenEJB, Directory,
> etc...). So it's really just a matter of where we think those
> features should be maintained.
>
> On Mon, Feb 14, 2011 at 10:23, Charles Moulliard <cm...@gmail.com> wrote:
>> Hi,
>>
>> I accept your remarks and agree with the point that features.cfg
>> should be keep clean or at least containing the standard/enterprises
>> files. But this is quite strange as EJB is also an Enterprise feature
>> for J2EE but not longer considered like that for OSGI World ;-)
>>
>> I very happy to hear that we are open to setup a repo containing such
>> information like probably features used for Web projects (Struts,
>> MyFaces, Spring WebFlow, Apache Wicket, ....) or anything else like
>> Apache FTP, Apache James for SMTP, ....
>>
>> Regards,
>>
>> Charles
>>
>>
>> On Sat, Feb 12, 2011 at 11:17 AM, <jb...@nanthrax.net> wrote:
>>> -1
>>>
>>> Karaf is a container. The features should be provided by tiers projects.
>>>
>>> However, I wonder if a kind of a Enterprise Feature Repository (EFR) couldn't be interesting.
>>> For instance, a EFR could host features or kar for several applications/projects.
>>> In karaf, we register a set of EFRs. The EFR gives all hosted features. In karaf, we don't have to define each features descriptor, we simply define a EFR location.
>>> Like this:
>>> - the projects could register their features
>>> - there is no more features descriptors url to add, just a EFR location
>>>
>>> It's kind of extensions of maven repo used for features.
>>>
>>> My 2 cents ;)
>>>
>>> Regards
>>> JB
>>> -----Original Message-----
>>> From: Charles Moulliard <cm...@gmail.com>
>>> Date: Fri, 11 Feb 2011 18:15:59
>>> To: dev<de...@karaf.apache.org>
>>> Reply-To: dev@karaf.apache.org
>>> Subject: OpenEJB and Enterprise Features
>>>
>>> Hi,
>>>
>>> OpenEJB project has created a feature file to deploy their bundles.
>>> This should be an excellent candidate for our Enterprise Features file
>>> and a compagnion for Aries. Is it better to copy / paste their
>>> features in our file or to point to their feature file in
>>> org.apache.karaf.features.cfg ?
>>>
>>> + 1 : to copy/paste = add their file in karaf.features.cfg
>>> - 1 : to copy/paste = add their file in karaf.features.cfg
>>>
>>> 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: OpenEJB and Enterprise Features
Posted by Guillaume Nodet <gn...@gmail.com>.
I think you misunderstood.
I have always wanted to deploy OpenEJB on ServiceMix Kernel / Karaf
since ages, but never had the time to work on it, so I do think it's a
great idea.
So it's not about OpenEJB, it's about Karaf not being able to bring
all projects as dependencies. Karaf isn't Geronimo, and I think we
should try to push the maintenance of those feature descriptors back
to the corresponding projects (Aries, Camel, CXF, OpenEJB, Directory,
etc...). So it's really just a matter of where we think those
features should be maintained.
On Mon, Feb 14, 2011 at 10:23, Charles Moulliard <cm...@gmail.com> wrote:
> Hi,
>
> I accept your remarks and agree with the point that features.cfg
> should be keep clean or at least containing the standard/enterprises
> files. But this is quite strange as EJB is also an Enterprise feature
> for J2EE but not longer considered like that for OSGI World ;-)
>
> I very happy to hear that we are open to setup a repo containing such
> information like probably features used for Web projects (Struts,
> MyFaces, Spring WebFlow, Apache Wicket, ....) or anything else like
> Apache FTP, Apache James for SMTP, ....
>
> Regards,
>
> Charles
>
>
> On Sat, Feb 12, 2011 at 11:17 AM, <jb...@nanthrax.net> wrote:
>> -1
>>
>> Karaf is a container. The features should be provided by tiers projects.
>>
>> However, I wonder if a kind of a Enterprise Feature Repository (EFR) couldn't be interesting.
>> For instance, a EFR could host features or kar for several applications/projects.
>> In karaf, we register a set of EFRs. The EFR gives all hosted features. In karaf, we don't have to define each features descriptor, we simply define a EFR location.
>> Like this:
>> - the projects could register their features
>> - there is no more features descriptors url to add, just a EFR location
>>
>> It's kind of extensions of maven repo used for features.
>>
>> My 2 cents ;)
>>
>> Regards
>> JB
>> -----Original Message-----
>> From: Charles Moulliard <cm...@gmail.com>
>> Date: Fri, 11 Feb 2011 18:15:59
>> To: dev<de...@karaf.apache.org>
>> Reply-To: dev@karaf.apache.org
>> Subject: OpenEJB and Enterprise Features
>>
>> Hi,
>>
>> OpenEJB project has created a feature file to deploy their bundles.
>> This should be an excellent candidate for our Enterprise Features file
>> and a compagnion for Aries. Is it better to copy / paste their
>> features in our file or to point to their feature file in
>> org.apache.karaf.features.cfg ?
>>
>> + 1 : to copy/paste = add their file in karaf.features.cfg
>> - 1 : to copy/paste = add their file in karaf.features.cfg
>>
>> 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: OpenEJB and Enterprise Features
Posted by Charles Moulliard <cm...@gmail.com>.
Hi,
I accept your remarks and agree with the point that features.cfg
should be keep clean or at least containing the standard/enterprises
files. But this is quite strange as EJB is also an Enterprise feature
for J2EE but not longer considered like that for OSGI World ;-)
I very happy to hear that we are open to setup a repo containing such
information like probably features used for Web projects (Struts,
MyFaces, Spring WebFlow, Apache Wicket, ....) or anything else like
Apache FTP, Apache James for SMTP, ....
Regards,
Charles
On Sat, Feb 12, 2011 at 11:17 AM, <jb...@nanthrax.net> wrote:
> -1
>
> Karaf is a container. The features should be provided by tiers projects.
>
> However, I wonder if a kind of a Enterprise Feature Repository (EFR) couldn't be interesting.
> For instance, a EFR could host features or kar for several applications/projects.
> In karaf, we register a set of EFRs. The EFR gives all hosted features. In karaf, we don't have to define each features descriptor, we simply define a EFR location.
> Like this:
> - the projects could register their features
> - there is no more features descriptors url to add, just a EFR location
>
> It's kind of extensions of maven repo used for features.
>
> My 2 cents ;)
>
> Regards
> JB
> -----Original Message-----
> From: Charles Moulliard <cm...@gmail.com>
> Date: Fri, 11 Feb 2011 18:15:59
> To: dev<de...@karaf.apache.org>
> Reply-To: dev@karaf.apache.org
> Subject: OpenEJB and Enterprise Features
>
> Hi,
>
> OpenEJB project has created a feature file to deploy their bundles.
> This should be an excellent candidate for our Enterprise Features file
> and a compagnion for Aries. Is it better to copy / paste their
> features in our file or to point to their feature file in
> org.apache.karaf.features.cfg ?
>
> + 1 : to copy/paste = add their file in karaf.features.cfg
> - 1 : to copy/paste = add their file in karaf.features.cfg
>
> 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: OpenEJB and Enterprise Features
Posted by jb...@nanthrax.net.
-1
Karaf is a container. The features should be provided by tiers projects.
However, I wonder if a kind of a Enterprise Feature Repository (EFR) couldn't be interesting.
For instance, a EFR could host features or kar for several applications/projects.
In karaf, we register a set of EFRs. The EFR gives all hosted features. In karaf, we don't have to define each features descriptor, we simply define a EFR location.
Like this:
- the projects could register their features
- there is no more features descriptors url to add, just a EFR location
It's kind of extensions of maven repo used for features.
My 2 cents ;)
Regards
JB
-----Original Message-----
From: Charles Moulliard <cm...@gmail.com>
Date: Fri, 11 Feb 2011 18:15:59
To: dev<de...@karaf.apache.org>
Reply-To: dev@karaf.apache.org
Subject: OpenEJB and Enterprise Features
Hi,
OpenEJB project has created a feature file to deploy their bundles.
This should be an excellent candidate for our Enterprise Features file
and a compagnion for Aries. Is it better to copy / paste their
features in our file or to point to their feature file in
org.apache.karaf.features.cfg ?
+ 1 : to copy/paste = add their file in karaf.features.cfg
- 1 : to copy/paste = add their file in karaf.features.cfg
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: OpenEJB and Enterprise Features
Posted by Achim Nierbeck <bc...@googlemail.com>.
-1; for embedding this external feature into karaf
+1 on the central "knowledge" base about external features available :)
One side node, OpenEJB with Karaf, Interesting something I always wanted
to try :)
> Also -1; I'm also for the repository approach! (I've also added something like
> this already to the roadmap page)
>
> kind regards,
> andreas
>
> On Fri, Feb 11, 2011 at 07:37:52PM +0100, Guillaume Nodet wrote:
>> -1 If they have it, why would we copy it and have to maintain it. We
>> can simply point users to it, can't we ?
>> I don't really want to maintain a feature file for all projects people
>> could be interested in, that doesn't scale and will only add more
>> dependencies and problems to our builds. I'd like to push the aries
>> one back to aries too.
>>
>> However, having a wiki page or a non released file we could features
>> repository file that would have links to other repositories would be
>> fine imho.
>> For example, we could imagine having somewhere a repository with only
>> other repositories in it. Users coud just add that one and that would
>> give them access to lots of projects.
>>
>> On Fri, Feb 11, 2011 at 18:15, Charles Moulliard<cm...@gmail.com> wrote:
>>> Hi,
>>>
>>> OpenEJB project has created a feature file to deploy their bundles.
>>> This should be an excellent candidate for our Enterprise Features file
>>> and a compagnion for Aries. Is it better to copy / paste their
>>> features in our file or to point to their feature file in
>>> org.apache.karaf.features.cfg ?
>>>
>>> + 1 : to copy/paste = add their file in karaf.features.cfg
>>> - 1 : to copy/paste = add their file in karaf.features.cfg
>>>
>>> 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: OpenEJB and Enterprise Features
Posted by Andreas Pieber <an...@gmail.com>.
Also -1; I'm also for the repository approach! (I've also added something like
this already to the roadmap page)
kind regards,
andreas
On Fri, Feb 11, 2011 at 07:37:52PM +0100, Guillaume Nodet wrote:
> -1 If they have it, why would we copy it and have to maintain it. We
> can simply point users to it, can't we ?
> I don't really want to maintain a feature file for all projects people
> could be interested in, that doesn't scale and will only add more
> dependencies and problems to our builds. I'd like to push the aries
> one back to aries too.
>
> However, having a wiki page or a non released file we could features
> repository file that would have links to other repositories would be
> fine imho.
> For example, we could imagine having somewhere a repository with only
> other repositories in it. Users coud just add that one and that would
> give them access to lots of projects.
>
> On Fri, Feb 11, 2011 at 18:15, Charles Moulliard <cm...@gmail.com> wrote:
> > Hi,
> >
> > OpenEJB project has created a feature file to deploy their bundles.
> > This should be an excellent candidate for our Enterprise Features file
> > and a compagnion for Aries. Is it better to copy / paste their
> > features in our file or to point to their feature file in
> > org.apache.karaf.features.cfg ?
> >
> > + 1 : to copy/paste = add their file in karaf.features.cfg
> > - 1 : to copy/paste = add their file in karaf.features.cfg
> >
> > 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: OpenEJB and Enterprise Features
Posted by Guillaume Nodet <gn...@gmail.com>.
-1 If they have it, why would we copy it and have to maintain it. We
can simply point users to it, can't we ?
I don't really want to maintain a feature file for all projects people
could be interested in, that doesn't scale and will only add more
dependencies and problems to our builds. I'd like to push the aries
one back to aries too.
However, having a wiki page or a non released file we could features
repository file that would have links to other repositories would be
fine imho.
For example, we could imagine having somewhere a repository with only
other repositories in it. Users coud just add that one and that would
give them access to lots of projects.
On Fri, Feb 11, 2011 at 18:15, Charles Moulliard <cm...@gmail.com> wrote:
> Hi,
>
> OpenEJB project has created a feature file to deploy their bundles.
> This should be an excellent candidate for our Enterprise Features file
> and a compagnion for Aries. Is it better to copy / paste their
> features in our file or to point to their feature file in
> org.apache.karaf.features.cfg ?
>
> + 1 : to copy/paste = add their file in karaf.features.cfg
> - 1 : to copy/paste = add their file in karaf.features.cfg
>
> 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