Change in JSP error handling in Tomcat5.0??

[Graba, Jan]

Hi.

While testing a JSP error page that was working fine 9 months ago, I found that 
the page is not now performing its function.
Instead of displaying an appropriate error message when the associated JSP 
receives alphabetic data instead of the integer data
that it is expecting, an HTTP 500 message saying that the data manipulation JSP 
cannot be displayed is generated by the browser. 

The simple application behaves fine when valid data is entered, and the JSP 
error page itself can be rendered directly (if a
suitable check is made for the implicit object 'exception' being equal to null).

Here is the (very ordinary) error page declaration line in the data 
manipulation JSP:
%@ page errorPage=AdderError.jsp %

Here is the (equally ordinary) associated line in the JSP error page:
%@ page isErrorPage=true %

The only changes that have taken place since I last tested these pages are the 
replacement of Java SDK1.4.2 with SDK1.5.0/5.0 and
the replacement of Tomcat 4.1 with Tomcat 5.0.

It seems highly unlikely that the change of SDK could have led to this problem, 
but I suppose that there may be some change to
Tomcat (or, more likely, version 2.4 of the servlet API) that has passed me by.

Can anybody shed light on the cause of this change in behaviour?

Any assistance would be greatly appreciated.

Cheers.
Jan

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: error-page directive

[Graba, Jan]

Hi, again.

I don't really think it makes any difference to this application, but I'm using 
J2SE, not J2EE. Though I am, of course, using a
web.xml file for my web application, nothing in this file need reference the 
error page. At least, that was the case with version
2.3 of the servlet API under Tomcat 4.1, since the error page worked 
faultlessly under that. Is 2.4 more restrictive? Is an
error-page tag now mandatory? Is this change documented? Since I currently have 
only servlet and servlet-mapping tags in my
web.xml, can I simply place the tag where I wish?

Sorry for the proliferation of fairly trivial questions.

Thanks in anticipation.

Cheers.
Jan

-Original Message-
From: David Smith [mailto:[EMAIL PROTECTED] 
Sent: 01 March 2005 13:27
To: Tomcat Users List
Subject: Re: error-page directive


The order matters.  It's a requirement that comes from validating the 
web.xml against a DTD -- not anything that Tomcat itself requires.  In 
the servlet 2.4 spec, they moved to valdating against a schema so order 
no longer matters.

--David

Ian van der Neut wrote:

On Tue, 1 Mar 2005 10:41:36 +0100, Ian van der Neut [EMAIL PROTECTED] 
wrote:
  

On Tue, 01 Mar 2005 10:32:42 +0100, Trond G. Ziarkowski 
[EMAIL PROTECTED] wrote:


Hi,

Have you tried to move your the error-page directive to between the 
welcome-file-list and taglib directives. Seem to remember this 
happening to me some time ago as well.
  

That seems to get rid of the message, but it doesn't seem to honour 
the directive, because I still get tomcats default exception 
stacktrace page.



The fact that it is not honoured seems to be because of a problem in 
the apperror.jsp file. Moving the error-page directive before the 
taglib directive solves the problem indeed.

Just curious, does order matter in web.xml? If so, where is this 
documented? Or is this just a bug?

Thank you very much,

Ian.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

  


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]