Hi all, Interesting discussion. I guess the question in general is how to properly avalonize a web application. Off course there is Sevak, but you'd need Phoenix for that. I have been working on some Catalina modules that provide Avalon (Fortress) support in tomcat hosted web applications. Basically my aim is to have Servlets (and possibly other Servlet container hosted objects such as JSPs and Filters) be able to implement (a subset of) the avalon lifecycle interfaces and get serviced transparently:
class MyServlet extends HttpServlet implements Serviceable IMO this would be the ideal way to add avalon support to a web application. Unforturnately there seems to be no way to accomplish this in a cross servlet container manner thru the public servlet API (ServletContext.getServlet() method is deprecated as of Servlet API 2.1 with no direct replacement). J�rg Schaible wrote: > > It is not guaranteed that a servlet > container uses only one instance of a servlet. He might even > create a new instance of it with each request (I had to deal > with such a beast). Therefore I propose the > ApplicationListner for the Avalon initialization. I can't find any reference to this class. Do you mean javax.servlet.ServletContextListener? Aaron Farr wrote: > > The concept of adding Servlet support to Avalon is interesting though. > Wouldn't have to be just HTTPServlet support either. Thought > I'm not sure what advantages this would have over just > hosting jetty or tomcat. There was a discussion a while ago on the Cocoon mailing list about the need for a thinner java based web container than the servlet ones that are around at the moment. Because for applications like Cocoon that depend on a servlet container to provide access to it over HTTP but that really don't need all the features that come with such an environment it would be much more efficient and elegant to have only a simple HTTP stack to manage incoming requests. Anton Tagunov wrote: > > III.b) create our own Avalon+HTTP beast > in the lines of our discussion here, under > this topic with Ulrich: > > UM> Yeah, obviously the servlet spec contains a lot of things that we > UM> don't need (JSP, deployment options...), but ServletRequest and > UM> ServletResponse support would be nice. Hurray! Count me in! :) Unico --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
