How about adding a "message" attribute to ProcessingNode, e.g:
<map:match pattern="page/*">
<map:generate type="jx" src="screens/{1}.xml" message="match is page/{1}"/>
which would output something like
sitemap: C:/cocoon/build/webapp/samples/sitemap.xmap:16:20: match is page/getNumberA.html
I like this very much!
+1
I don't like this and find it hacky. Using println in the flowscript is a useful technique and as I said I use it. But introducing official println equivalents all over the place will lead to floods of messages scrolling on the console or filling the logs. Wouldn't a unified debugger for the various languages cooperating in Cocoon (sitemap, jxtemplate, woody form definitions, etc) be more useful?
-0.9
Sylvain
While I like the concept for the exception handling (as this was already one of the biggest issues with Cocoon or hurdle to get Cocoon loved) I also don't like the println above. How does SunBow ("Cocoon Debugger: Stepping through the sitemap. Trace the XML stream and sitemap variables.") handle these things? Isn't it extensible?
Joerg
