On 13 Jan 2004, at 11:46, Torsten Curdt wrote:
It seems to me like this thread mixes concerns between error reporting (strack traces) and debugging or "processing monitoring" (knowing what's going on at a high level).
:) exactly
What I want is a way to know what my cocoon is doing at a level that I understand the basic programmatic steps. Just like log() in flow or log() in my java code, I want log() in my sitemap. What's wrong with that?
And if you like a debugger and want to write it, fine, I just never used it and never found the need for it.... but don't tell me "log in sitemap is hacky, we should come up with a debugger" because that's not how I want to work.
So it might be a good idea to have <map:log> write to a specific logging category ("cocoon.processing"), where calls to addCocoonStackTrace would be logged as well. The "cocoon.processing" log category would then give a very useful high-level view of what's going on.
true ...it might be a bit hard to read when you have more than one user hitting that machine though ;)
don't know about you, but when I develop I'm the only one hitting the cocoon instance I work on, so this is a nonissue, IMO.
-- Stefano.
