Smith [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, July 11, 2001 8:07 AM
Subject: Re: JSP calls instance method, bombs with odd message
Sachin--
I compared your working code to what I posted as best I could, and found
1
significant change: setting public on variable dynamicstring
Sachin--
I compared your working code to what I posted as best I could, and found 1
significant change: setting public on variable dynamicstring in the class file.
I changed that.
However, I'm still getting the same error.
Did I miss some other change? What version of Tomcat did you run it
Have a nice day.
With regards,
Sachin S. Khanna
http://www.emailanorder.com
- Original Message -
From: Martin Smith [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sunday, July 08, 2001 6:22 AM
Subject: JSP calls instance method, bombs with odd message
I'm going a little nuts with an error
Martin:
I'm no guru, but:
1) Try adding public in:
public String dynamicstring = firstdynamic;
2) I think I've heard that the Response has already been committed
message is not necessarily the real problem, but is a secondary (error
reporting) issue that arises sometimes when another
I'm going a little nuts with an error. The app is a single JSP, and the
error occurs when I try to call a Java class file I made. Using Tomcat
3.
Here's the message:
Error: 500
Location: /wpv3beta1.jsp
Internal Servlet Error:
