This usually points to a missing jar file or missing classes. By missing I mean either not available on the classpath, etc.
-----Original Message----- From: prophecy [mailto:[EMAIL PROTECTED] Sent: 22 March 2006 01:07 To: users@tomcat.apache.org Subject: Only a type can be imported. x.y.MyClass resolves to a package Generated servlet error: Only a type can be imported. x.y.MyClass resolves to a package This happens for every class used in the jsp page. It is a very strange occurence and appears to have happened after upgrading to Tomcat 5.5.16 and JDK 1.5.0_06 . Has anyone else come across these issues lately? I tried it with a fresh web application and still get this. -- View this message in context: http://www.nabble.com/Only-a-type-can-be-imported.-x.y.MyClass-resolves-to-a -package-t1321174.html#a3524514 Sent from the Tomcat - User forum at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
