I ran into this one as well. I have to check my home configuration, but I think you do have to add your jars to the project classpath - Eclipse/Sysdeo seem to effect the Tomcat classpath settings.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Thomas Kramer Sent: Thursday, 30 January 2003 9:24 AM To: [EMAIL PROTECTED] Subject: [OS-webwork] Problem with Eclipse and Tomcat Plugin Hi, I have a problem, runnung Eclipse 2.1 on W2K with the tomcat 4.12 plugin from Sysdeo. If I use the webwork classes in my project and start tomcat within the eclipse ide, tomcat returns the error "HTTP Status 503 - Servlet action is currently unavailable" after calling an webwork action. JSP pages run correctly. If I start tomcat normally with the "startup.bat" from the bin directory, everything works fine. Does anyone has experiences with eclipse, tomcat and webwork? Do I have to set other jars in the project-classpath, I only added the webwork.jar to the libraries in the projects java build path. Thanks for your help, Thomas Kramer ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
