Timothy Bennett wrote:
> To answer that, I'm going to have to read up on Tapestry and get back[EMAIL PROTECTED] wrote:
with you.
Picking this quote out of the Tapestry User's Guide:
[quote]
This can take some getting used to. You don't write servlets in Tapestry, you write listener methods. You don't build URLs to servlets either -- you use an existing component (such as DirectLink) and configure its listener parameter to invoke your listener method. What does a listener method do? It interacts with backend systems (often, stateless session EJBs) or does other bookkeeping related to the request and selects a new page to provide a response to the user ... basically, the core code at the center of a servlet.
[/quote]
Hmmmmm... this sound strangely similar to what we are trying to do with the HTTP facility for Merlin. The facility starts up a Jetty web server and then provides the plumbing to route HTTP requests to a special Avalon-Merlin *listener* components which happen to be a servlet. These listener components have access to the merlin service manager, and thus can interact with any other component deployed in the merlin component (back-end system). The components that the facility hands the request off to can do anything you want with the request and response.
Continuing to read....
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
