Technically that would work, but I really can't and don't want do that. For example, I might want to throw a SQLException for some reason, or another application specific-exception. For the latter I guess one could extend ProcessingException, but somehow that doesn't seem like a nice thing to do just because XSPs are inflexible.
From: Joerg Heinicke <[EMAIL PROTECTED]> Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: throwing non-ProcessingExceptions from XSPs Date: Sat, 23 Aug 2003 00:23:55 +0200
What about extending ProcessingException?
Joerg
Sonny Sukumar wrote:
Hi guys,
Is it possible to declare additional exception types to be thrown from the generate() method generated from an XSP? The generate code throws SAXException, IOException, ProcessingException by default. I thought that, since Cocoon 2.1 has improved support for handling various exception types (aside from ProcessingException) at the end of pipelines, that maybe one could maybe get away without wrapping exceptions in ProcessingException instances in XSPs.
If it is possible, how can one declare a specific exception type to be thrown using XSP syntax?
Thanks,
Sonny
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
_________________________________________________________________
Get MSN 8 and enjoy automatic e-mail virus protection. http://join.msn.com/?page=features/virus
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
