Based on the tutorials, it looks like I will have to bury the web navigation code into my java classes (Please correct me if I'm missing something). It's not a totally bad thing, but it's one reason I don't like Struts. If a page can be reached from multiple places then the context preparation code has to be in multiple places too.
One framework that really excels in this area is ActionServlet (http://www.actionframework.org/). All of the navigation and context-preparation logic is defined in XML. This is much cleaner and easier to understand the site flow (IMHO) than hunting around the java classes to figure out the conditions that control the site flow. My dream web application framework would be a cross of Tapestry and ActionServlet, but maybe I don't understand Tapestry well enough yet. Jonathan ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. ********************************************************************** ------------------------------------------------------- This sf.net email is sponsored by: See the NEW Palm Tungsten T handheld. Power & Color in a compact size! http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer
