Right. The issue is server side access to the class, not client side
through httpd.
The following link seems directly related to the OP's issue:
http://forum.java.sun.com/thread.jspa?threadID=567258&messageID=2944921
Essentially the class must be a valid bean declared public with a
default (no parameter), public constructor.
--David
Mark Thomas wrote:
Martin Gainty wrote:
David-
..he could also have execute/read permissions turned off in .htaccess
M-
Martin, you are talking nonsense and confusing the issue.
1) .htaccess is an httpd configuration feature that does not exist in
Tomcat
2) The OP made no mention of using httpd in his configuration
3) Even if httpd was being used, .htaccess mis-configuration would not
cause this error.
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]
