Re: Sevak Fork.

Paul,

> I'm not really sure what you're talking about here ?  Elementary Config  
> was done in the last commit.

Yes, I can see that. I was thinking of creating the Jetty Server 
(org.mortbay.jetty.Server) by giving it a standard Jetty configuration. 
This way it is possible to configure all things that can be configured 
for a normal Jetty installation in Jervlet-Jetty. It is somewhat 
limiting to have that config object with port, host etc. and in new 
stuff is included in Jetty the conf would perhaps need to be updated also.


The creation could look like:

import org.mortbay.jetty.Server;
import org.mortbay.xml.XmlConfiguration;

*****

private Server m_server;
private String m_jettyConfiguration;
private String m_jettyConfFile;

*****

m_server = ( Server ) new XmlConfiguration(
   m_jettyConfiguration ).newInstance();

or

m_server = new Server( m_jettyConfFile );



I would personally like to have this possibility to be able to take over 
running Jetty implementations with a Jervlet-Jetty. To do that all SSL 
and auth stuff must be configurable and the extra libs be included in 
Jetty-Jervlet, perhaps in an extended build. If it sounds good I can try 
to rework the old stuff after your recent commits. Some changes to 
AbstractJettyJervlet, AvalonJettyJervlet and PicoJettyJervlet shod do it.


//
Johan