1. timestamp
If you use a Servlet 2.3 servlet-engine you could device a simple filter and scan for url's. Not really clean, but should be working. 2. screens (events) 3. preprocessor I usually use one action per form. There is an attribute (parameter) in the action-mapping (struts-config) that you can easily check in the action (mapping.getParameter() ). That way the action knows how to prepare the page and how to evaluate it. 4. regions 5. cactus/unit testing 6. JNDI Struts or not, I tend to isolate this kind of functionality into a special helper-class. That way I can reuse the logic when I have to write a java-application, an applet or servlet,... Use a startup-servlet to initialize the helper and, if you want, do some prefetching. Additionally the servlet could be used as an administration-interface to control the helper. regards Alexander Jesse -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
