Re: Proposal to use OSGi for component modularity

> > Hi Ioannis, > > Any information you need from CloudStack to get started? For now, I am still trying to get more familiar with the project. By the way did you mentioned that you are going to switch to maven build or there were just thoughts about it? -- *Ioannis Canellos* * FuseSource

Re: Proposal to use OSGi for component modularity

27;m sure theres a mixed bag of those that want to contribute to varying degrees. This way the learning curve can be tackled quickly with help, and we can grow the community at the same time. --Alex > > > > -Original Message- > > From: Mohammad Nour El-Din [mailto:nour.

RE: Proposal to use OSGi for component modularity

Hi Ioannis, Any information you need from CloudStack to get started? --Alex > -Original Message- > From: Ioannis Canellos [mailto:ioca...@gmail.com] > Sent: Sunday, June 03, 2012 9:17 AM > To: cloudstack-dev@incubator.apache.org > Subject: Re: Proposal to use OSG

RE: Proposal to use OSGi for component modularity

arted. Any help in this area to get us started would be great. --Alex > -Original Message- > From: Mohammad Nour El-Din [mailto:nour.moham...@gmail.com] > Sent: Friday, June 01, 2012 3:53 AM > To: cloudstack-dev@incubator.apache.org > Subject: Re: Proposal to use OSGi

Re: Proposal to use OSGi for component modularity

> > I like to gather opinions about > > 1. Whether to use OSGi or there should be other frameworks to consider? > Regardless of wether you are going to use OSGi or not, providing valid OSGi metadata and making sure that the project is OSGi-ready is generally a good thing to do. 2. If OSGi, whethe

Re: Proposal to use OSGi for component modularity

Hi Marcel... On Fri, Jun 1, 2012 at 2:10 AM, Marcel Offermans < marcel.offerm...@luminis.nl> wrote: > Hello Mohammad, > > On May 31, 2012, at 20:36 , Mohammad Nour El-Din wrote: > > > But from what you said Frank, and what others proposed, I think you don't > > need that kind of modularity facili

Re: Proposal to use OSGi for component modularity

Hello Mohammad, On May 31, 2012, at 20:36 , Mohammad Nour El-Din wrote: > But from what you said Frank, and what others proposed, I think you don't > need that kind of modularity facilitated by OSGi or like technologies, I > believe all what we need then is: > > 1- Good design +1 > 2- Good doc

RE: Proposal to use OSGi for component modularity

ovides, which has the advantage that in the future we can > leverage these features if required > > > > > > > -Original Message- > > > From: Chris Custine [mailto:chris.cust...@gmail.com] > > > Sent: Wednesday, May 30, 2012 11:17 PM > > > To: cloud

Re: Proposal to use OSGi for component modularity

hing it provides, which has the advantage that in the future we can leverage these features if required > > > -Original Message- > > From: Chris Custine [mailto:chris.cust...@gmail.com] > > Sent: Wednesday, May 30, 2012 11:17 PM > > To: cloudstack-dev@incubator.apache.org > &g

RE: Proposal to use OSGi for component modularity

compiling would be good enough. > -Original Message- > From: Chris Custine [mailto:chris.cust...@gmail.com] > Sent: Wednesday, May 30, 2012 11:17 PM > To: cloudstack-dev@incubator.apache.org > Subject: Re: Proposal to use OSGi for component modularity > > On Wednesday,

Re: Proposal to use OSGi for component modularity

On Thu, May 31, 2012 at 9:16 AM, Chris Custine wrote: > On Wednesday, May 30, 2012 at 12:32 PM, Frank Zhang wrote: > > I have some different thoughts here > > > > > On Tuesday, May 29, 2012 at 10:29 PM, Alex Huang wrote: > > > > > > > CloudStack is built as a product with modularity enforced by >

Re: Proposal to use OSGi for component modularity

On Wednesday, May 30, 2012 at 12:32 PM, Frank Zhang wrote: > I have some different thoughts here > > > On Tuesday, May 29, 2012 at 10:29 PM, Alex Huang wrote: > > > > > CloudStack is built as a product with modularity enforced by interfaces. > > > It > > had its own component management via Comp

RE: Proposal to use OSGi for component modularity

> > On May 31, 2012, at 0:59 AM, Frank Zhang wrote: > > > Another problem I want to raise here is the class loader issue. > > There are bunch of places in CloudStack using Class.forName(), I am sure > ClassNotFoundException would then be our best friend. > > Class.forName() in general won't work

Re: Proposal to use OSGi for component modularity

On May 31, 2012, at 0:59 AM, Frank Zhang wrote: > Another problem I want to raise here is the class loader issue. > There are bunch of places in CloudStack using Class.forName(), I am sure > ClassNotFoundException would then be our best friend. Class.forName() in general won't work in OSGi, that

RE: Proposal to use OSGi for component modularity

sday, May 30, 2012 11:32 AM > To: cloudstack-dev@incubator.apache.org > Subject: RE: Proposal to use OSGi for component modularity > > I have some different thoughts here > > > On Tuesday, May 29, 2012 at 10:29 PM, Alex Huang wrote: > > > > > CloudStack is b

Re: Proposal to use OSGi for component modularity

Alex, one of the mentors, pointed me to this thread. I've been doing OSGi projects for over 10 years now and am involved in Felix, ACE and Celix (all OSGi related projects here at Apache). > From: Alex Huang > > CloudStack is built as a product with modularity enforced by interfaces. It > ha

RE: Proposal to use OSGi for component modularity

I have some different thoughts here > On Tuesday, May 29, 2012 at 10:29 PM, Alex Huang wrote: > > > CloudStack is built as a product with modularity enforced by interfaces. It > had its own component management via ComponentLocator. While that > framework made it easy for a small group of develop

Re: Proposal to use OSGi for component modularity

This is a very timely discussion indeed… I had a recent discussion with several others in the jclouds community about how interesting it would be to rework Cloudstack on an osgi component model. So it seems this is not just a fantasy? ;-) I would love to help with this effort so I will happi