Re: Tomcat 5.5 Upgrade Problems

[mslinn]

I have found exactly the same problem, and it's bad news.  The web
application has LOTS of JSPs, and I really don't want to jam them in the
root directory.  Is there a solution?
--
View this message in context: 
http://www.nabble.com/Tomcat-5.5-Upgrade-Problems-t1404562.html#a4379330
Sent from the Tomcat - User forum at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Tomcat 5.5 Upgrade Problems

[Hassan Schroeder]

On 4/6/06, prophecy [EMAIL PROTECTED] wrote:


I've been getting this error after upgrading from Tomcat 5.0 to Tomcat 5.5:

Only a type can be imported. com.x.MyClass resolves to a package



And the only solution, that I found after hours of banging my head on the
keyboard, is to put the jsp files in the root context directory.  For
instance, if the jsp files are at /index.jsp, it works fine.  If it's at
/somedir/index.jsp , it can't find the classes in the WEB-INF/classes dir.
This is very strange behaviour, am I the only one that has seen this?


I have multiple instances of Tomcat (5.5.9 - 5.5.17) running on
various platforms, and haven't seen this anywhere.

And I just did a quick test of moving a page with imports deeper
into the directory structure, with no effect.

So there's something else going on; without more specific info
it's hard to say what. Can you make a simple WAR of a test case?

--
Hassan Schroeder  [EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]