Hi Daniel,
a problem during development when using the blocks-protocol is that you
don't see a stacktrace when some problem occurs inside the block called
via the BlockSource. You get an empty XML/HTML stream sent to the browser.
As far as I can see, the nice exception/stacktrace page displayed by
Cocoon ("Problem in creating the Request") is generated in Cocoon's
MultiPartFilter that is by default configured in the web.xml. This
filter is not running when a BlockServlet is called via a BlockSource
connection. Would it be somehow possible to add such a filter there? Or
at least to include the manageException() code of the MultiPartFilter in
the BlockSource/Connection?
I had a look at it but couldn't figure out, where the exception thrown
by the contained SitemapServlet could be catched in the blocks-fw code.
Alex
--
Alexander Klimetschek
http://www.mindquarry.com
