On Tue, 11 Sep 2001 05:57, Paul Hammant wrote:
> >The HTTPServer would register the callback method to handle the
> > ServerSockets. It should delegate the requests as it sees fit--with WAR
> > mounting, Servlet routing, default FileServlet, and cacheing.  Hopefully,
> > you get the overall picture here.
>
> But I am only on about modelling.
>
> Think about our (one day) EJB server.  It needs a webserver.  Not just
> that it needs a WAR file capable web server.
>
> <block name="fred-ejb" .....
>    <depends role="org.apache.avalon.services.WARFileHTTPServer"/>
> </block>
>
> It should not matter whether the assembler uses Tomcat or Jetty, it
> should just work.  To pad out WARFileHTTPServer a bit more it should have :
>
>   void deployWAR(String key, File warFile) throws WARDeploymentException;
>   void deployWAR(String key, URL warFile) throws WARDeploymentException;
>   void deployWAR(String key, InputStream warFile) throws
> WARDeploymentException ;
>   void deployWAR(String key, ClassLoader warFile) throws
> WARDeploymentException;
>   void unDeployWAR(String key) ..;

Sounds good except I wouldn't make the interface extend anything. I guess the 
problem is that without a real-life test-case I don't think we are going to 
have an easy time defining a generic interface. For instance the in-JVM EJB 
container has a fairly incestuos relationship with servlet container and they 
have to share all sorts of resources (ie ClassLoader hierarchy is very 
specific as in shared JVM resources etc).

It may be a good idea to have a bash at it but I would mark it as possibly 
changing in future or highly volatile or whatever - at least until we see 
some reali-life testing. Thoughts?

-- 
Cheers,

Pete

--------------------------------------------------------------
"Science is like sex: sometimes something useful comes out, 
but that is not the reason we are doing it" -- Richard Feynman
--------------------------------------------------------------

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to