I'm hoping you are not telling me that this stack trace is not going to be
suppressed. Since this is "normal" behavior I'd expect that at most an
informational log message would be generated.
I'll rephrase: instead of this ResourceNotFoundException (which is coming out of cocoon: source), SourceNotFoundException should be thrown. Once this fixed, it will not be logged as an error.
Vadim
Ralph
-----Original Message----- From: Vadim Gritsenko [mailto:[EMAIL PROTECTED] Sent: Thursday, December 18, 2003 1:12 PM To: [EMAIL PROTECTED] Subject: Re: multiple catalogue search
Ok, now that's "just" issue of proper exception handling.
I18n correctly catches SourceNotFoundException, but in this case we got SAXException which is wrapped around ResourceNotFoundException. I need to find a place where this original ResourceNotFoundException was thrown and see for a correct place to convert it to SourceNotFoundException (as per Source contract).
You can re-run your test with my last commit and see how stacktrace will look like. It should show now original stacktrace of the ResourceNotFoundException.
Vadim
