You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by Alex Karasulu <ao...@bellsouth.net> on 2005/06/14 02:05:37 UTC
[general] Using OSGi with ApacheDS (was Re: Summer of Code Application)
I thought I'd open up a separate thread wrt using an OSGi based container.
Alex Karasulu wrote:
> 13). Possible IoC Container Strategy
>
> ApacheDS does not use a container and we have tried to be container
> independent to avoid introducing specificities.
> We want the server to be as embeddable as possible WRT the existing
> containers out there. Hence we do not want say the Geronimo folks to
> have to introduce container specific code if they want to embed
> ApacheDS. Plus we don't want protocol implementors and committers on
> the core to have to worry about learning a new container and its
> semantics. Things are already hard.
> If we can keep the container code separated from the core then perhaps
> we can ship with a default container for the final executable
> service. Why try? We loose a lot not having a default container.
> What do we loose:
>
> Aspects like ...
>
> o management interfaces
> o logging
> o configuration
> o hot deployment of components
> o ...
>
> Right now Enrique has attracted my attention to OSGi. He makes
> excellent points about it. It's the container of choice for embedding
> in appliances and other devices. Plus it's got a written
> specification to it endorsed by major companies like IBM, Cisco and
> many others. This is what makes it unique in comparison to the
> Geronimo GBeans, Spring and other Avalon, ComponentHaus productions.
> All these containers are great btw so I'm not putting them down and we
> still reserve the right to integrate with them as well. However OSGi
> seems like the best candidate to Enrique and I.
Thoughts, comments?
BTW OSGi is a spec and many container implementations exist out there.
That's just one of the many reasons why it is so attractive. Enrique
has pointed me to the Oscar and Knopplerfish implementations.
Some folks in both these communities were interested in the idea of an
ASF based implementation. Perhaps we can cross post or get some
specific email addresses to include these people.
Alex
Re: [general] Using OSGi with ApacheDS (was Re: Summer of Code Application)
Posted by Trustin Lee <tr...@gmail.com>.
2005/6/14, Alex Karasulu <ao...@bellsouth.net>:
>
> > What do we loose:
> >
> > Aspects like ...
> >
> > o management interfaces
> > o logging
> > o configuration
> > o hot deployment of components
> > o ...
> >
> > Right now Enrique has attracted my attention to OSGi. He makes
> > excellent points about it. It's the container of choice for embedding
> > in appliances and other devices. Plus it's got a written
> > specification to it endorsed by major companies like IBM, Cisco and
> > many others. This is what makes it unique in comparison to the
> > Geronimo GBeans, Spring and other Avalon, ComponentHaus productions.
> > All these containers are great btw so I'm not putting them down and we
> > still reserve the right to integrate with them as well. However OSGi
> > seems like the best candidate to Enrique and I.
I like the basic idea of using OSGi, but many ppl prefers to use
lightweight IoC containers or hard-code it to use OSGi framework until now.
So I think we can approach in both way actually.
Possible way is to embed OSGi framework and provide frontend POJO, or we
could provide limited funcionality in POJO, and full in OSGi.
WDYT?
Trustin
--
what we call human nature is actually human habit
--
http://gleamynode.net/
RE: [general] Using OSGi with ApacheDS (was Re: Summer of Code Application)
Posted by "Noel J. Bergman" <no...@devtech.com>.
> Are you suggesting adding JMX alone will solve these problem
> minus the logging?
Possibly, yes. See also: JSR-77 and JSR-88. And talk with Dain. But I
would go for a container that supports JMX, and then use JMX.
--- Noel
Re: [general] Using OSGi with ApacheDS (was Re: Summer of Code Application)
Posted by Alex Karasulu <ao...@bellsouth.net>.
Noel J. Bergman wrote:
>>>What do we loose:
>>>Aspects like ...
>>>o management interfaces
>>>o logging
>>>o configuration
>>>o hot deployment of components
>>>
>>>
>
>Except for logging, that sounds like JMX.
>
Are you suggesting adding JMX alone will solve these problem minus the
logging?
-Alex
Re: [general] Using OSGi with ApacheDS (was Re: Summer of Code Application)
Posted by Alex Karasulu <ao...@bellsouth.net>.
Noel J. Bergman wrote:
>>>What do we loose:
>>>Aspects like ...
>>>o management interfaces
>>>o logging
>>>o configuration
>>>o hot deployment of components
>>>
>>>
>
>Except for logging, that sounds like JMX.
>
Are you suggesting adding JMX alone will solve these problem minus the
logging?
-Alex
RE: [general] Using OSGi with ApacheDS (was Re: Summer of Code Application)
Posted by "Noel J. Bergman" <no...@devtech.com>.
> > What do we loose:
> > Aspects like ...
> > o management interfaces
> > o logging
> > o configuration
> > o hot deployment of components
Except for logging, that sounds like JMX.
--- Noel