Have a look at the a.o.c.util.location package. That provides the machinery to print the sitemap component / filename / line number / column in an exception traceback. That should allow you to learn how to get hold of these values at component entry. Instrument the code with logger.debug calls and enable it in the logging config.
HTH, Alfred. From: Sands Alden Fish [mailto:sa...@mit.edu] Sent: Dienstag, 6. Dezember 2011 16:42 To: dev@cocoon.apache.org Subject: Sitemap Node Traversal Logging? Hey all, I'm trying to get Cocoon (2) to spit out a log entry of each sitemap file/line/line-number that it hits while processing a pipeline request. I've been digging around in the logkit config and sitemap logger configs, but there doesn't seem to be an easy way to do this globally. Any suggestions? I will patch Cocoon source, if necessary... Thanks! -- sands fish Senior Software Engineer MIT Libraries Technology Research & Development sa...@mit.edu<mailto:sa...@mit.edu> E25-131 The content of this e-mail is intended only for the confidential use of the person addressed. If you are not the intended recipient, please notify the sender and delete this e-mail immediately. Thank you.
