[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [equinox-dev] servlet container incubator
- From: Scott Lewis <slewis@xxxxxxxxxxxxx>
- Date: Tue, 21 Feb 2006 14:41:52 -0800
- Delivered-to: email@example.com
- User-agent: Mozilla Thunderbird 1.0 (Windows/20041206)
Hi Jeff and all,
Jeff McAffer wrote:
FYI, one of the students working with the Equinox team has done an
extensible JMX based mechanism that is really pretty cool. We hope to
have that in the incubator soon.
OK, great. We would like to jump on that as soon as it is available.
If we can get it sooner than it is available :) then please just let me
> > > 2) I've seen in passing discussion of a consistent programmatic
> > > interface for startup bundle initialization but haven't
> > > read the whole
> > > thread. Where is that work at this point?
> Hmm... I'm not sure what you're referring to.
> Right now a combination of a hard-coded config.ini and the
> update.configurator are used similar to RCP.
Is this a reference to the "how do I startup all the bundles that my
bundle depends on" and "controlling the startup order" discussions?
Yes. I've seen these go by on equinox-dev, but haven't been able to
read all of them.
If so, there really hasn't been a conclusion there. Several people
have pointed out that depending on start order etc is somewhat less
than optimal. Having said that, there are still issues with how
things actually do get started. The spec is silent. Some frameworks
have a policy of starting everything. Some start nothing. Clearly
more work/thinking is needed in this area.
OK, fair enough!
> > > 5) Is there jaas-based authentication work in 3.2M5? If
> > so, is there a description of how to use it somewhere?
> I've been using declarative and custom (non-JAAS) authentication.
> JAAS support would be nice but it's not in place currently.
Not in M5. We are working hard to get a contribution from IBM in this
space. Not sure where it is in the process right now. Depending on
when it comes in it may or may not be an official part of 3.2.
OK. We (ECF) are definately interested in using the jaas authentication
specifically (as opposed to authorization...which, although it would be
great is not as important to us as seeing authentication in 3.2). FWIW.
Thanks Jeff, Simon, and Simon,