RE: Tomcat 3.2 throwing a VerifyError at me
It would appear to me that you are trying to create an instance of a class (using Class.newInstance()) that doesn't have a matching contructor to how you are trying to load it. If I remember correctly, newInstance only works with No-Argument constructors. Check for this, and if its not in your code, check the generated java - maybe Jasper is generating this call? Randy -Original Message- From: Rajnish Bhaskar [mailto:[EMAIL PROTECTED]] Sent: Monday, February 12, 2001 9:41 AM To: [EMAIL PROTECTED] Subject: Tomcat 3.2 throwing a VerifyError at me I didn't get a reply to this before, so I'm resending it. Raj. Hi all, I've been using Tomcat 3.1 for a quite a long time now, and I thought that I'd finally give 3.2.1 a try since it's (finally) out of beta. I've set up Tomcat on a Windows NT4 machine with Sun JDK 1.2 and added my webapp to the server.xml file as follows: !-- /ITEU context added by RAJ -- context path="/ITEU" docBase="webapps/ITEU" crossContext="true" trusted="true" debug="0" reloadable="false" /context I then went through my app to ensure that everything is still working, and although most of the JSPs are working fine, when it comes to one of them, I get a VerifyError exception: /ITEU/html/manager/displayquestions.jsp Internal Servlet Error: javax.servlet.ServletException: (class: html/manager/_0002fhtml_0002fmanager_0002fdisplayquestions_00 02ejspdisplayquestions_jsp_1, method: _jspService signature: (Ljavax/servlet/http/HttpServletRequest;Ljavax/servlet/http/HttpServle tResponse;)V) Incompatible object argument for function snip Root cause: java.lang.VerifyError: (class: html/manager/_0002fhtml_0002fmanager_0002fdisplayquestions_00 02ejspdisplayquestions_jsp_1, method: _jspService signature: (Ljavax/servlet/http/HttpServletRequest;Ljavax/servlet/http/HttpServle tResponse;)V) Incompatible object argument for function at java.lang.Class.newInstance0(Native Method) snip I've gone back and checked this against Tomcat 3.1 and it works fine. I'm guessing that this is some sort of security thing that is different between 3.1 and 3.2, or there's some setting that I've missed, but I can't see what it is. Can someone help? TIA, Raj. -- Rajnish Bhaskar [EMAIL PROTECTED], http://i.am/rajy IT Education Unit, University of Glasgow http://www.iteu.gla.ac.uk/ -- Only buffoons refer to the Internet as the Information Superhighway. -- (The Rough Guide to the Internet 1999) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: Tomcat 3.2 throwing a VerifyError at me
It would appear to me that you are trying to create an instance of a class (using Class.newInstance()) that doesn't have a matching contructor I never call Class.newInstance() at all in my code. maybe Jasper is generating this call? How do I check this, and how do I stop it from happening? Sorry for all the questions, maybe I should just leave the system alone. It sems quite happy with Tomcat 3.1. Thanks, Raj. -- Rajnish Bhaskar [EMAIL PROTECTED], http://i.am/rajy IT Education Unit, University of Glasgow http://www.iteu.gla.ac.uk/ -- Arms alone are not enough to keep the peace it must be kept by men. -- John Fitzgerald Kennedy, 1962 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: Tomcat 3.2 throwing a VerifyError at me
In the work directory will be a .java file that will correspond to your jsp file. (The name will be managled, but its fairly straight forward which file is which). You won't be able to change how Jasper works, but knowing which class it wants to create with a no-arg constructor will help solve the problem. Randy -Original Message- From: Rajnish Bhaskar [mailto:[EMAIL PROTECTED]] Sent: Monday, February 12, 2001 10:01 AM To: [EMAIL PROTECTED] Subject: RE: Tomcat 3.2 throwing a VerifyError at me It would appear to me that you are trying to create an instance of a class (using Class.newInstance()) that doesn't have a matching contructor I never call Class.newInstance() at all in my code. maybe Jasper is generating this call? How do I check this, and how do I stop it from happening? Sorry for all the questions, maybe I should just leave the system alone. It sems quite happy with Tomcat 3.1. Thanks, Raj. -- Rajnish Bhaskar [EMAIL PROTECTED], http://i.am/rajy IT Education Unit, University of Glasgow http://www.iteu.gla.ac.uk/ -- Arms alone are not enough to keep the peace it must be kept by men. -- John Fitzgerald Kennedy, 1962 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: Tomcat 3.2 throwing a VerifyError at me
An easy way to find it is to introduce an error in the JSP and look at Jaspers error message, which includes the full path to the file. -Original Message- From: Randy Layman [mailto:[EMAIL PROTECTED]] Sent: Monday, February 12, 2001 9:38 AM To: [EMAIL PROTECTED] Subject: RE: Tomcat 3.2 throwing a VerifyError at me In the work directory will be a .java file that will correspond to your jsp file. (The name will be managled, but its fairly straight forward which file is which). You won't be able to change how Jasper works, but knowing which class it wants to create with a no-arg constructor will help solve the problem. Randy -Original Message- From: Rajnish Bhaskar [mailto:[EMAIL PROTECTED]] Sent: Monday, February 12, 2001 10:01 AM To: [EMAIL PROTECTED] Subject: RE: Tomcat 3.2 throwing a VerifyError at me It would appear to me that you are trying to create an instance of a class (using Class.newInstance()) that doesn't have a matching contructor I never call Class.newInstance() at all in my code. maybe Jasper is generating this call? How do I check this, and how do I stop it from happening? Sorry for all the questions, maybe I should just leave the system alone. It sems quite happy with Tomcat 3.1. Thanks, Raj. -- Rajnish Bhaskar [EMAIL PROTECTED], http://i.am/rajy IT Education Unit, University of Glasgow http://www.iteu.gla.ac.uk/ -- Arms alone are not enough to keep the peace it must be kept by men. -- John Fitzgerald Kennedy, 1962 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]