To be honest, I'm not sure I'd do it that way again. My Avalon component also implements the Container interface by passing requests to the underlying Container, but that turned out not to be too useful. The only "benefit" is that it is configured in cocoon.xconf vs. web.xml. I preferred that at the time as I have had no reason to modify Cocoon's web.xml, but that will be changing.
Ralph -----Original Message----- From: Ugo Cei [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 11, 2004 8:40 AM To: [EMAIL PROTECTED] Subject: Re: MVC Framework - options? Ralph Goers wrote: > I didn't actually write our lifecycle container, but the developer who did > told me that Spring comes with a sample showing how to integrate it into any > servlet by providing a routine that gets specified in web.xml. He actually > did that first, but I preferred the method described above. Spring does indeed provide a servlet listener for initializing an application context [1]. I am curious as to why you preferred wrapping in in an Avalon component. Ugo [1]: http://www.springframework.org/docs/reference/beans.html#context-create --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
