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]
