on 6/19/03 6:18 AM Matt Sergeant wrote:
> On Wed, 18 Jun 2003, Stefano Mazzocchi wrote:
>
>
>>>What about a stacktrace like this:
>>>
>>>Error <foo bar> occurred at:
>>>Java: org.apache.cocoon.components.SomeComponent.Configure:237:4
>>> Sitemap: /test/sitemap.xmap:25 (map:generate src="..."
>>>type="SomeComponent")
>>> Sitemap: /test/sitemap.xmap:24 (map:match pattern="someresource")
>>> Sitemap: /sitemap.xmap:20 (map:mount check-reload="yes" src="{1}/"
>>>uri-prefix="{1}" - {1}="test")
>>> Sitemap: /sitemap.xmap:19 (map:match pattern="*/**")
>>> URI: cocoon://test/someresource
>>> XSLT: /xsl/foo-bar.xslt:454:53 (document())
>>> XSLT: /xsl/foo-bar.xslt:25:10 (template: /)
>>> Sitemap: /sitemap.xmap:30 (map:transform src="xsl/foo-bar.xslt")
>>> Sitemap: /sitemap.xmap:28 (map:match pattern="page.html")
>>> URI: page.html
>>
>>oh, god, I would *LOVE* to see that implemented. A *real* Cocoon
>>stacktrace instead of a useless java one.
>
>
> Go one step further. Make your stack trace XML and make it so you can
> apply XSLT to it. AxKit does this, and it's incredibly useful.
We are already doing this for the error handler, but the stacktrace
itself is not xml-ized (and I think that xml-izing a java stacktrace
wouldn't be that useful...) but in the above case, yeah, full
semantization would allow very nice display pages to be created easily.
--
Stefano.
