On Wednesday 04 January 2006 09:47, tmarx wrote: > 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?
My first reaction is to ask why? If you are chasing a specific problem, then maybe - but in the first instance don't you just want to let Tapestry get on with what it does without really checking on it. If it gets into a problem, it puts up a nice screen with lots of debug information anyway. If you concentrate on your applications interaction with the framework - so Page Event Listeners, (and any other listenerers) seem to be good breakpoints. Sometimes instead of letting a property remain abstract, I make it a real routine and put breakpoints there. -- Alan Chandler http://www.chandlerfamily.org.uk Open Source. It's the difference between trust and antitrust. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
