> > How about the Context approach?  e.g.
> > ...
> > public Cocoon(CocoonContext context) {}
> > ...
> > The Main and CocoonServlet objects would populate the proxy object,
> > so that anything that as the number of arguments grow or shrink,
> > we don't have to change the signature.
> 
> I'm not sure about this - it could be overkill, but I do see
> your thinking.

Well, I am thinking about how to get the ServletContext object to
Cocoon, and see if I can do the getResource() for things inside
jars.  Basically, I want to be able to embed all the jars inside
the Webapp classpath, and have it work with all servlet engines.

It's easier said than done, though.