On Fri, 2002-08-30 at 16:45, William Brogden wrote: > > On 30 Aug 2002, Bruno Dumon wrote: > > > > > Captor is a tool that lets you see the XML being produced by each > > > transformer in a Cocoon pipeline. Currently it only works > > with Cocoon > > > 2.03, and not yet with 2.1. Implementation-wise captor > > works like the > > > profiler included with cocoon, but instead of storing the > > time spent in > > > each transformer, it stores the SAX-events that came out of each > > > transformer. > > > > > > For more information and download, see: > > > > > > http://outerthought.net/captor.html > > > > Whats the difference between Captor and the LogTransformer that > comes with Cocoon 2.0.1 ? It sits in the pipeline and logs the > SAX events to a file. >
Captor automatically records everything happenening in all pipelines, it is not needed to edit the sitemap and add a transformer everywhere. Captor can be disabled/enabled by only changing the eventpipeline implementation in the cocoon.xconf. Also, the LogTransformer logs SAX events, while captor shows the actual XML. LogTransformer is therefore more usefull to debug buggy transformers that generate invalid SAX-events. Captor is also easier to use, you don't need to search through logfiles, it provides a clear overview of everything that is "captored". Captor is especially usefull if you have pipelines with lots of transformers, it then makes it very easy to see what each transformer exactly does. > I wrote an extension that also logs the state of many > "pipeline variables" - its going to be in the Cocoon > book from Sybex (pub in October) or I can send anybody a copy. > > [EMAIL PROTECTED] > Author of Soap Programming with Java - Sybex; ISBN: 0782129285 > -- Bruno Dumon http://outerthought.org/ Outerthought - Open Source, Java & XML Competence Support Center [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
