Guys, as you might have noticed I've added some features to reduce the the burden when it comes to debugging XSP. (I suffered from that again when looking into the latest esql bug - and it pissed me off that much that I needed to change something on that ;-)
As for one I added the source code excerpts to the LanguageException so it shows you the actual source code that surround the compilation error. (this was brought up on cocoon-users lately) Well, now I wanted to pretty-print the LanguageException as other Exceptions are already... unfortunately I didn't understand what I found... Thanks to Sylvain who gave me some help off the list but seems I don't understand that mechanism yet... Looking at the stacktrace of the LanguageException I see: ...components.treeprocessor.TreeProcessor.process(TreeProcessor.java:289) ...Cocoon.process(Cocoon.java:591) ...servlet.CocoonServlet.service(CocoonServlet.java:1002) ...javax.servlet.http.HttpServlet.service(HttpServlet.java:853) Currently the Beautified-Exceptions are constructed in the Cocoon.service method by sending a notification. Shouldn't the LanguageException already get caught by the last catch clause and become beautified, too? It's a catch(Exception) around the processing of request?! What did I miss here? -- Torsten --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
