The Http Facility

Gang,

I am working on the HTTP Facility for Merlin, and want to be introducing the 
following changes;

1. Having a configuration with <listener> at the 'root' level seems bound to 
create messy config files over time, esp when new configuration parameters 
are introduced.
I want us to deprecate (and possibly remove, since it is not yet released) 
this way and instead use (2).

2. Introduce <listeners> as a configuration node, with the above mentioned 
<listener> nodes under it.

3. Introduce 
  <servlets>
    <servlet>
      <component>/somecontainer/anothercontainer/mycomponent</component>
      <url>/my-url</url>
    <servlet>
  </servlets>
The implementation is as straight forward as I could imagine, meaning;
In DefaultServer.initialize() store these mappings into a map, and when the 
ContainmentModelHandler calls the DefaultServer.register( ComponentModel 
model ), the component path gets translated prior to registering it to the 
Jetty server. If there is no defined <url> for a component, the component 
path is used like before.

WDYT?

Users; I am also interested to hear about any other requests that may exist, 
while I am digging around in the code anyway.

Cheers
Niclas

-- 
   +------//-------------------+
  / http://www.bali.ac        /
 / http://niclas.hedhman.org / 
+------//-------------------+