Christian Haul wrote:
On 12.Dec.2002 -- 10:08 AM, [EMAIL PROTECTED] wrote:Anyway, whatever the outcome I look forward to this new development as it certainly is something that is needed badly. Perhaps Gianugo and Nicola could provide some details on what they are thinking of?What we were discussing is a possibility to debug the pipeline.
[...]
Yup, Gianugo and I have expanded on this last possibility, and I already have some code that shows it's doable.The third and most promising variant would be to place the debug transformer at the end of the pipeline. It could pop up a window showing the current event and a button to continue. Since processing is stopped until the SAX event call returns, it would be possible to single step the pipeline in conjunction with the log transformer. Of course, a deluxe debug transformer could show the generated document so far and event allow to inspect the objectModel. Actually, I believe that showing the Document in a tree control would be relatively simple. Adding an option whether to confirm every event, or only special events (like endDocument) would be nice as well. And together with the XPathProcessor's selectSingleNode it should be relatively simple to break on XPath expressions as well.
Basically, the concept is to create a DebuggingPipeline, and a DebuggingCachingPipeline, that insert special debugging connectors between the components of the pipeline. These log all events, and interact with a client debugger via an Avalon CocoonDebuggerComponent that works as a proxy.
In this way we can see all that is happening in the pipeline event per event, component per component, and be able to set xpath breakpoints.
:-)
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
