What are the best break points for quickly debugging a tapestry application in general?
Has anyone got a quick summary of the interactions between the ServletContainer, Tapestry and Hivemind? Tapestry receives a HTTP request from the Servlet Container, does all the Tapestry internal stuff and returns an HTML response. So I am sure the HTTP request receiption would be a good breakpoint for the first step and the passing of the html response a good end point. What about inside of Tapestry? Which methods in which classes should I set the break points for checking: - resolution of the page name - reading of the page template - looping through the components - filling the page template with the data I think if errors occur the following cases are possible and most likely (please add some more cases if you find some!) - error reading a template - error processing a template - error reading data in general (connection issues, timeouts, "not-expected silentlly-ignored-errors") - error reading a component - error processing a component For every case I am looking for a debug point.....(in order to find out why my webapplication stalls) Thanks! Toby -------------------- m2f -------------------- Sent from www.TapestryForums.com Read this topic online here: <<topic_link>> http://www.tapestryforums.com/viewtopic.php?p=12644#12644 -------------------- m2f --------------------
