I hope the attached diagram is more accurate and others find it useful. Cheers, Matt
Vincent Massol wrote: > > Matt, > > * I misread point 8.1. Actually, it was correct (I thought you said > iterate through all the test cases). Can you put it back on your diagram > ;-). Sorry. > > * Point 7 is called by JspTestRedirector and not by jspRedirector.jsp > > * Point 8 is a doGet() that's correct but the intent is to "execute the > test" > > * Point 9 and 10 are done by JspTestRedirector, not jspRedirector.jsp > > * Point 11 is correct (you can say 1..N, it was correct !). > > * Point 12 is executed by JspTestRedirector > > * Between 13 and 14 you need to add an arrow from jspRedirector.jsp to > JspTestRedirector that says "get test results" (this is the equivalent > of point 8) > > Everything else is fine. Most of the remarks above are minor, so I think > you are really now understanding how it works ! ;-) > > * I think such a diagram really makes sense to understand Cactus. Maybe > we can only show the classes that in direct interaction with the > XXXTestCase (i.e. the classes that the Cactus user sees). In that case, > we should drop the JspTestRedirector which is an internal classes (also > there are lots of other internal classes that we are not showing so it's > not fair to show this one only ... :-)). If we remove the > JspTestRedirector, I think the diagram is perfect for a newcomer to > understand how it works. > > Then we simply need to instanciate it for the 3 redirectors > (ServletRedirector, jspRedirector.jsp and FilterRedirector). > > What do you think ? > > Thanks Matt for your help ! > > -Vincent > <snipped>
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
