HI, I've run into a problem in JDBC and I want to see the error text on the errorpage I've declared in my JSP but when the errorpage loads, the code <%= exception.getMessage() %> prints the output 'null' on the errorpage. Does this mean the exception details are not getting passed properly from the first JSP? I know the exception has to do with a resultset from a bean not being scrollable - but I'll post THAT question over on the JDBC forum. How would I get the bean to tell the JSP the details of the error? Thanks in advance ------------------ Terry Doyle Sun Certified Programmer for Java 2 Platform
On your error page, did you indicate that it is the error page?
I'd think it would be fairly vendor specific but the exception oject may not be populated without it... Dave. [This message has been edited by David O'Meara (edited October 14, 2001).]
William Brogden
Author and all-around good cowpoke
Rancher
Joined: Mar 22, 2000
Posts: 12271
1
posted
0
I suppose it is possible that the Exception does not have a message so null is the right output. You might try exception.printStackTrace( out ) to get more information. Bill ------------------ author of:
HI, Thanks to both of you. David: <%@page isErrorPage="true"%> is already on the page Bill: I inserted the code as you suggested and I got the following error message: An error occurred at line: 22 in the jsp file: /jsp/errorpage.jsp Generated servlet error: C:\Tomcat4\work\localhost\examples\jsp\errorpage$jsp.java:66: Incompatible type for method. Can't convert javax.servlet.jsp.JspWriter to java.io.PrintWriter. out.print( exception.printStackTrace( out ) ); ^ 1 error Any ideas? Thanks very much,
------------------ Terry Doyle Sun Certified Programmer for Java 2 Platform
As a complete stab in the dark and after looking at the description for AbstractMethodError, I'm guessing you should stop Tomcat, recompile everything you can then restart Tomcat
Thrown when an application tries to call an abstract method. Normally, this error is caught by the compiler; this error can only occur at run time if the definition of some class has incompatibly changed since the currently executing method was last compiled.
(Good luck, I'm going home so hopefully William Brogden or another capable soul will assist) Dave.
Terence Doyle
Ranch Hand
Joined: May 30, 2001
Posts: 328
posted
0
Thanks. I restarted and recompiled everything but to no avail. I'll have to go over the java.sql docs to see what abstract method I am invoking or not to create this error. Bye,
------------------ Terry Doyle Sun Certified Programmer for Java 2 Platform