[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [equinox-dev] servlet container incubator

Hi Scott,
> Is there a way to plugin code to detect whether it's running 
> via this servlet container bridge or whether it's running in 
> Eclipse or some other OSGI environment?

For OSGi environment use "org.osgi.framework.vendor" (as the other Simon
recommended ;)

The HttpService should be registered with some properties that will help
you determine the provider.
Currently the Servlet Bridge implementation does not register a
service.pid, service.vendor, or service.description but will shortly
(waiting to finalize a bundle name first). This is probably the way to
go longer-term.

If you need to do something short-term you can check to see if the
BridgeServlet is visible in your class space.


> > The ECF team is using the equinox servlet container 
> > incubator (thanks
> > Simon) to build/deploy a simple 'generic' collaboration server to 
> > ecf.eclipse.org (for testing and usage by project team members).
> >
> > We've got the basics running...servlet container, bridge, OSGI 
> > runtime, our server bundles, etc.  We're just working through some 
> > firewall issues at eclipse.org, some config changes/generalizations 
> > for our server, and then it will be running constantly/consistently 
> > there...and made available to Eclipse Foundation project teams for 
> > online team collaboration.
That's great. Let me know if you'd like a hand with anything.

> >
> > A couple of quick questions about the osgi runtime in 
> servlet container:
> >
> > 1) Is anyone working on an html interface for the OSGI console...if 
> > so, where is that?  We would like to start/stop/restart, 
> > etc., etc our 
> > server bundle(s) without using the servlet container and 
> > OSGI console.  
> > I've seen the httpconsole pointers on the incubator page 
> > and haven't 
> > worked with it yet, but probably will start...but wanted to 
> > know what 
> > work is going on here
For now I'd recommend looking at the httpconsole. There certainly are
plans to create an http/html interface however things haven't really got
going yet.

> > 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.

> > 3) Are there any  changes/additions for 3.2M5?
In terms of new features for the Servlet Bridge there were few changes
visible at the API level.
One framework level change that I'm excited about is that we can now run
multiple independent instances in the same VM. e.g. In M4 we were
restricted to a single webapp but now you can safely run multiple
equinox webapps.

> > 4) What are the plans WRT the servlet container incubator?
Good question.
For my part I'd like to more-or-less follow the 3.2 plan and really just
tie up loose ends with the functionaility as it exists today. Perhaps if
there's time (and consensus) these components can graduate from the
incubator however a process still has to be defined so for the time
being this is a work in progress. 

There are also some really cool new ideas coming both for servlet
containers and other server-side environments that can continue in the
incubator until they're ready to move out.

> >Is there any need/desire to show/show (off) such 
> > a server running ECF (in ~ production) at EclipseCon?
Production is good ;) Do you have something particular in mind?

> > 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.

-Simon
 
     This message may contain privileged and/or confidential information.  If you have received this e-mail in error or are not the intended recipient, you may not use, copy, disseminate or distribute it; do not open any attachments, delete it immediately from your system and notify the sender promptly by e-mail that you have done so.  Thank you.