Farr, Aaron wrote:
<snip/>
Okay, did I miss anything? Questions? Comments?
I've been catching up on this thread and I've been looking over the Servlet 2.3 in relation to event and listener interfaces - in particular the servlet context events. Given that we can associate a listener (in a standard way), and that listener can intercept during startup and shutdown of the servlet, then it seems to me that the same same listener should be able to apply any supplimentary stages that a servlet may need.
I have not tried to do this but this is what I'm thinking:
1. listener gets creation event
2. listener get classname of the servlet
3. listener reads in meta-info from descriptor
corlocated with servlet class
4. listener gets meta-data from its own configuration
or some external source
5. listener builds artifacts form lifecycle processing
of the servlet and applies stages (e.g. servicing
of the servlet)
5. listener intercepts destroy even and handles
decommissioning of the artifacts conosumed by the
servletHas anyone tried anything like this?
Cheers, Steve.
--
Stephen J. McConnell mailto:[EMAIL PROTECTED] http://www.osm.net
Sent via James running under Merlin as an NT service. http://avalon.apache.org/sandbox/merlin
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
