This may be something for a bugzilla report, but I looked at the source
of org.apache.jasper.compiler.Generator. The real exception generated
is eaten in favor of the very unhelpful message you received.
The possible original exceptions may have been one of:
java.lang.ClassNotFoundException - the class is not in
WEB-INF/classes/internet/database or a jar in WEB-INF/lib probably not
your issue since it works from jsps located in the webapp's root directory.
java.lang.NoSuchMethodException - if no default constructor was found, I
think you've already said one was present.
java.lang.SecurityException - if the security manager is active and
denying access. Hmmm..... is tomcat running under a security manager?
--David
Mark Thomas wrote:
Lars Nielsen Lind wrote:
Here is the error-report shown in the browser:
The stack trace suggests the class cannot be instantiated. Hmm. Odd.
Can you create a simple test case that reproduces this? You won't be
able to post a war to the list so feel free to send it to me directly.
Mark
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
