Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: AW: AW: [equinox-dev] [sec] JAAS framework dependency on Eclipse

yeah, eclipsecon.org seems a bit busted...  I put the presentation on the equinox documents site
        http://www.eclipse.org/equinox/documents
Look for
        http://www.eclipse.org/equinox/documents/eclipsecon2006/Best%20Practices%20for%20Programming%20Eclipse%20and%20OSGi.pdf

Jeff



"Arthur van Dorp" <Arthur.vanDorp@xxxxxxxxx>
Sent by: equinox-dev-bounces@xxxxxxxxxxx

09/05/2007 03:31 AM

Please respond to
Equinox development mailing list <equinox-dev@xxxxxxxxxxx>
To
"Equinox development mailing list" <equinox-dev@xxxxxxxxxxx>
cc
Subject
AW: AW: [equinox-dev] [sec] JAAS framework dependency on Eclipse





Hi all

If providing both OSGi services and extension points is cheap in terms
of complexity/maintenance efforts then it sounds just perfect. I'm not
yet well versed enough in this area to judge the pros and cons the
different approaches offer.

Jeff, do you have a link to the EclipseCon talk? The links I've found
were dead.

OSGi services and the whiteboard pattern sounds to me like a natural
replacement for things like the CallbackHandler extension point. But I
don't know the other approaches (yet).

Regards

Arthur

Jeff McAffer wrote:
>
> All of the standard discussions should follow here.  lazy activation?
>  public/private contracts, white board models, ...  BJ and I did an
> EclipseCon talk in 2006 comparing some of the different approaches.  
> There are real usecases for both.  
>
> While using services can be convenient as services are built in, if
you
> follow that argument then one should not use Declarative Services as
> that support is not built in!   Perhaps the right answer is to
> standardize the extension registry ;-)
>
> Why pick?  It would be cool to support both.  Running on a bare
> framework is interesting in certain situations.  Using extensions on
the
> other hand gives some additional flexibility when configuring in
product
> scenarios (3.4 is slated to include some product customization
> infrastructure designed to declaratively glue things togther in new
> contexts)
>
> Jeff
>
>
>
> *"Matt Flaherty" <mwflaher@xxxxxxxxxx>*
> Sent by: equinox-dev-bounces@xxxxxxxxxxx
>
> 09/04/2007 04:54 PM
> Please respond to
> Equinox development mailing list <equinox-dev@xxxxxxxxxxx>
>
>
>  
> To
>  Equinox development mailing list <equinox-dev@xxxxxxxxxxx>
> cc
>  
> Subject
>  Re: AW: [equinox-dev] [sec] JAAS framework dependency on Eclipse
>
>
>  
>
>
>
>
>
>
> It's purely historical. Though I haven't thought through a design on
> OSGi services in detail, I can't think of a reason that it couldn't
work
> off the top of my head. Transitioning to services is certainly a
design
> we can consider going forward.
>
> -matt
>
> ---
> Matt Flaherty
> Security Project Lead, Lotus Notes & Eclipse Equinox
> External: _http://www.eclipse.org/equinox/incubator/security/_
> Internal: _https://cs.opensource.ibm.com/projects/eclipsesec/_
>
> equinox-dev-bounces@xxxxxxxxxxx wrote on 09/04/2007 02:24:33 PM:
>
>  > I think the more general point here is why are extensions being
used
> here
>  > instead of services (which already come built into the OSGi
> framework) as
>  > the means of connecting the various players of the JAAS framework?
Is
>  > there something about the JAAS framework design that cannot be
done, or
>  > done well, with services?
>  >
>  > Sure one can install the registry (and its dependent bundles) on
the
> OSGi
>  > framework and use them, but why introduce that coupling unless it
> truly is
>  > necessary? I would like to think that we may want to include the
JAAS
>  > framework design in the OSGi spec. But I don't see that OSGi
specified
>  > version of a JAAS framework will be based upon extensions.
>  > --
>  >
>  > BJ Hargrave
>  > Senior Technical Staff Member, IBM
>  > OSGi Fellow and CTO of the OSGi Alliance
>  > hargrave@xxxxxxxxxx
>  >
>  > office: +1 386 848 1781
>  > mobile: +1 386 848 3788
>  >
>  >
>  >
>  >
>  > Pascal Rapicault <Pascal_Rapicault@xxxxxxxxxx>
>  > Sent by: equinox-dev-bounces@xxxxxxxxxxx
>  > 2007-09-04 13:48
>  > Please respond to
>  > Equinox development mailing list <equinox-dev@xxxxxxxxxxx>
>  >
>  >
>  > To
>  > Equinox development mailing list <equinox-dev@xxxxxxxxxxx>
>  > cc
>  >
>  > Subject
>  > Re: AW: [equinox-dev] [sec] JAAS framework dependency on Eclipse
>  >
>  >
>  >
>  >
>  >
>  >
>  > The extension registry is an OSGi bundle, to that respect it runs
on any
>  > OSGi implementation.
>  > And for curious, it even runs without OSGi.
>  >
>  > PaScaL
>  >
>  >
>  >  
>  >   From:       "Matt Flaherty" <mwflaher@xxxxxxxxxx>  
>  >  
>  >   To:         Equinox development mailing list
> <equinox-dev@xxxxxxxxxxx>  
>  >  
>  >  
>  >   Date:       09/04/2007 10:58 AM  
>  >  
>  >   Subject:    Re: AW: [equinox-dev] [sec] JAAS framework dependency
on
>  > Eclipse
>  >  
>  >
>  >
>  >
>  >
>  >
>  >
>  > In the bug:
>  >
>  > _https://bugs.eclipse.org/bugs/show_bug.cgi?id=202156_
>  >
>  > Chris rightly points out that I may have been heavy-handed with
'pure' ;)
>  >
>  > Certainly the registry can be used in other environments.. Though
I've
>  > never tried it, the framework may very well work if you simply
> include the
>  > registry. Let me know if there is anything I can do to help get
your
>  > environment up and running.
>  >
>  > -matt
>  >
>  > ---
>  > Matt Flaherty
>  > Security Project Lead, Lotus Notes & Eclipse Equinox
>  > External: _http://www.eclipse.org/equinox/incubator/security/_
>  > Internal: _https://cs.opensource.ibm.com/projects/eclipsesec/_
>  >
>  > equinox-dev-bounces@xxxxxxxxxxx wrote on 09/04/2007 10:11:25 AM:
>  >
>  > > That answers my other question as well. Thanks.
>  > >
>  > > I'm going to file a bug right now and will contribute code if I
can
> come
>  > > up with something generic.
>  > >
>  > > I wonder whether the OSGi specification has already hooks
available to
>  > > put something like framework wide authentication.
>  > >
>  > > Thanks again and regards
>  > >
>  > > Arthur
>  > >
>  > > Matt Flaherty wrote:
>  > > >
>  > > > The authentication code currently relies on extension points to
>  > > > contribute the JAAS artifacts, so I don't believe it will
currently
>  > > work
>  > > > in a pure OSGi environment.
>  > > >
>  > > > Nothing is currently planned in this direction - primarily
because no
>  > > > one has asked yet... Requirements (via bugzilla) and
> contributions are
>  > >
>  > > > both welcome :)
>  > > >
>  > > > ---
>  > > > Matt Flaherty
>  > > > Security Project Lead, Lotus Notes & Eclipse Equinox
>  > > > External: _http://www.eclipse.org/equinox/incubator/security/_
>  > > > Internal: _https://cs.opensource.ibm.com/projects/eclipsesec/_
>  > > >
>  > > > equinox-dev-bounces@xxxxxxxxxxx wrote on 09/04/2007 09:33:34
AM:
>  > > >
>  > > >  > Hi all
>  > > >  >
>  > > >  > I'm looking for a way to leverage the authentication
functionality
>  > > >  > provided by JAAS for an application running on Equinox (not
>  > > depending on
>  > > >  > the rest of Eclipse). Is it possible to leverage the Equinox
>  > > Security
>  > > >  > framework for this or is it necessary to use the (Eclipse
> specific)
>  > > >  > extension points it provides to use it? Or are there any
plans on
>  > > making
>  > > >  > it a "pure" OSGi bundle?
>  > > >  >
>  > > >  > Regards
>  > > >  >
>  > > >  > Arthur
>  > > >  >
>  > > >  > _______________________________________________
>  > > >  > equinox-dev mailing list
>  > > >  > equinox-dev@xxxxxxxxxxx
>  > > >  > _https://dev.eclipse.org/mailman/listinfo/equinox-dev_
>  > > >
>  > > >
>  > > >
>  > >
>
------------------------------------------------------------------------
>  > > >
>  > > > _______________________________________________
>  > > > equinox-dev mailing list
>  > > > equinox-dev@xxxxxxxxxxx
>  > > > _https://dev.eclipse.org/mailman/listinfo/equinox-dev_
>  > >
>  > > _______________________________________________
>  > > equinox-dev mailing list
>  > > equinox-dev@xxxxxxxxxxx
>  > > _https://dev.eclipse.org/mailman/listinfo/equinox-dev_
>  > _______________________________________________
>  > equinox-dev mailing list
>  > equinox-dev@xxxxxxxxxxx
>  > _https://dev.eclipse.org/mailman/listinfo/equinox-dev_
>  >
>  >
>  > _______________________________________________
>  > equinox-dev mailing list
>  > equinox-dev@xxxxxxxxxxx
>  > _https://dev.eclipse.org/mailman/listinfo/equinox-dev_
>  >
>  >
>  > _______________________________________________
>  > equinox-dev mailing list
>  > equinox-dev@xxxxxxxxxxx
>  >
>
_https://dev.eclipse.org/mailman/listinfo/equinox-dev___________________
_____________________________
> equinox-dev mailing list
> equinox-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/equinox-dev
>
>
>
------------------------------------------------------------------------
>
> _______________________________________________
> equinox-dev mailing list
> equinox-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/equinox-dev

_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev

Back to the top