Here is how the current version of our debugger works (as shown in Gent): 1) It is a remote debugger. This means that the client (the eclipse plugin) connects to the Cocoon side of things using a socket.
2) As the request is processed by Cocoon, an adapted TreeProcessor sends events to the client. 3) It is a "2-phase" degugger. The first phase allows you to follow the route the request takes through the sitemap. This can happen step-by-step (or more exactly, component by component). The second phase then provides the xml document between each component in the sitemap. Visible on the client. In addition the currently available sitemap variables are also displayed on the client. So as you can see from this very rough description the concept is different - and of course the plugin is an eclipse plugin. Matthew --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
