I think it would be very nice to have a "standard" web.xml that goes beyond
a monolithic servlet.
But which registry will it work on in a configuration with multiple
servlets?
Henrik
----- Original Message -----
From: "Jesse Kuhnert" <[EMAIL PROTECTED]>
To: "Tapestry development" <[email protected]>
Sent: Thursday, August 17, 2006 3:32 PM
Subject: Re: Servlet Listener APIs...
Sure, sounds good to me :) (so long as the configuration is intuitive and
comes along with free documentation ;) )
On 8/17/06, James Carman <[EMAIL PROTECTED]> wrote:
All,
I have an idea for allowing users to more easily plug into the servlet
API
for lifecycle events. What if we create a new listener which can be
configured in the web.xml file that implements all of the servlet
listener
interfaces (HttpSessionAttributeListener and the like)? The listener
would
delegate to a pipeline configured in HiveMind (it'd look up the registry
on
the context). Then, a hivemodule could contribute to the pipeline they
want
in order to avoid having to plug stuff into the web.xml file. This would
make it easier to make hivemodules more "dropinnable" as they wouldn't
need
the user to add anything special to their web.xml file.
James
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Jesse Kuhnert
Tapestry/Dojo/(and a dash of TestNG), team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
