Steve Kirk wrote:
> At a guess, you are seeing the
> UnavailableException manifested as a 404 error in your
> browser, like this: "HTTP Status 404 - Servlet hemlock is not
> available", rather than an UnavailableException ?
Yes, exactly. Which isn't a problem -- except I can't find the *actual
Steve Kirk wrote:
> ...I think you'll find that the Tomcat error page (or your
> own custom error page, if configured) will automatically
> strip the outer ServletException layer off and report the
> underlying UnavailableException.
That's a possible workaround. But the JavaDocs are pretty cl
QM wrote:
> On Fri, Oct 22, 2004 at 06:44:07PM -0400, [EMAIL PROTECTED] wrote:
>> ...the message I specified in the exception I
>> threw does not show up -- not in the logs, not when I reload the
>> servlet in the manager, not on the page when I try to run the
>> servlet. I searched all the availa
