river-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sam Chance <sgcha...@gmail.com>
Subject Re: OSGi RFC 119 Distributed OSGi - (Was [RE: OSGi and Jini])
Date Tue, 14 Jul 2009 23:12:09 GMT

It is not my desire or intention to try to play "technology ping-pong."  I'm
only introducing another viewpoint.  Frankly, I don't have time to read
long, verbose emails.  I've touted enough OSGi technology attributes to
intrigue those who might be interested in learning more.  The answers to
your questions can be found on the OSGi Alliance's web site - and I promise
you there are solid answers.  Additionally, a number of books that provide
ample OSGi coverage are either recently published or nearing publication.

Oracle, Sun, IBM, SpringSource, JBoss, Progress, Paremus, ProSyst and others
offer a lot of informative OSGi literature as well. Neal Bartlett also
provides a lot of OSGi resources.  Eclipse [Equinox] and Apache Felix are
great places as well.

Happy Learning! :-)


On Tue, Jul 14, 2009 at 6:49 PM, Gregg Wonderly <gregg@wonderly.org> wrote:

> Sam Chance wrote:
>> In fact, OSGi does help a lot with "Classpath Hell".
> I didn't see a reply from my earlier request for more information on the
> issues that the OSGi experienced think OSGi helps the most with regarding
> this issue. I'd really like to see what issues you all have had and that
> OSGi has addressed.
> Is it just that packaging encloses the set of things you need to make
> things work and you don't have to worry about that, or is it something else?
>  Many containers use ClassLoader hierarchies of various shapes to isolate
> and "interrelate" different types of package structures.  I'm just
> interested in knowing more about the issues and benefits you all recognize
> from your experiences.
> > OSGi also adds another layer of security above the standard Java.
> What do you feel is important about this?  Authentication vs Authorization
> issues would be great to have your opinions and experience on.
> > Versioning is a "first-class function" in OSGi.
> This is a big deal for separating old and new.  I think we have a good bit
> of this in the PreferredClass mechanisms in Jini 2.x so that implementations
> can be  forced into use for bug fixing and interfacing with different
> versions of difference services.  Is there anything else beside classloader
> based separation that you all find important in what OSGi provides?
> Gregg Wonderly

Sam Chance
443-694-5293 (m)
410-694-0240 x108 (o)

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message