Re: [jervlet-patch] Make Jervlet-Jetty accept external configurations

Johan, Peter,

I'm not ignoring the patch and roadmap ideas, just very busy with a 
client's deadline.  I should have some time to try the patch on, etc, 
sometime tomorrow or friday.

--
Ryan Hoegg
ISIS Networks
http://www.isisnetworks.net

peter-4lf8KW9E9MLMqX/[email protected] wrote:

>Hiya,
>
>Looks good. Ryan - what do you think?
>
>
>----- Original Message -----
>From: "Johan Sjöberg" <johan.sjoberg-KK16lzWueydWk0Htik3J/[email protected]>
>To: <[email protected]>
>Sent: Tuesday, November 11, 2003 6:18 PM
>Subject: [jervlet-patch] Make Jervlet-Jetty accept external configurations
>
>
>  
>
>>Hi!
>>
>>Here is the first patchset to make Jetty-Jervlet accept external
>>configurations.
>>
>>This has been done so far:
>>
>>-Addition of two new Jetty Server creators
>>-Configuration logic added to AvalonJettyJervlet to except external
>>configurations
>>-Addition of a new AvalonJettyJervlet configuration schema (was missing!)
>>-Addition of an example configuration file
>>-Possibility to set the system parameter "jetty.home" (can be considered
>>bad by some)
>>-Small cleanups to the tops of AbstractJettyJervlet and
>>AvalonJettyJervlet plus fixes to other files that these broke.
>>-demoserver now uses AvalonJettyJervlet instead of JettyJervlet
>>-Minimal tests of AvalonJettyJervlet in Loom-current and a slightly
>>older version.
>>
>>
>>Theoretically nothing in PicoJettyJervlet should be broken and
>>demoserver now seems to work again. Next I would like to:
>>
>>-Make the log redirecting and access logging configurable in
>>AvalonJettyJervlet
>>-Remove JettyJervlet (that only extends AvalonJettyJervlet) and its
>>configuration schema
>>-Change demoserver (alt create new module) to be more release like for
>>the avalon/loom release already now. This means a new name, and empty
>>documented configuration files, etc. Otherwise very close to demoserver.
>>-Change the configuration in AvalonJervletJetty to take something like:
>><socketlisteners>
>>   <socketlistener>
>>      <host/>
>>      <port/>
>>      <maxthreads/>
>>      <minthreads/>
>>   </socketlistener>
>></socketlisteners>
>>instead of all those in the root level. This way many listeners could be
>>added to a Jetty Server.
>>-Set the default port (8080) in AvalonJervletJetty to -1.
>>-Clean up some parts of the code according to some standard (what should
>>be used btw?)
>>
>>
>>Could someone give some input on this?
>>
>>
>>Cheers,
>>
>>//
>>Johan
>>
>>    
>>



-------------------------------------------------------
This SF.Net email sponsored by: ApacheCon 2003,
16-19 November in Las Vegas. Learn firsthand the latest
developments in Apache, PHP, Perl, XML, Java, MySQL,
WebDAV, and more! http://www.apachecon.com/