tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 10036] - Unable to resolve a class name without a package definition
Date Thu, 20 Jun 2002 19:22:00 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10036>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10036

Unable to resolve a class name without a package definition





------- Additional Comments From ian779@darwinsys.com  2002-06-20 19:21 -------
Kin-Man wrote:>The servlet generated by jasper is in package org.apache.jsp.  As such,
>it won't be able to reference any class that is not in a package. I first thought Kin-Man
was wrong on this, but he's right.You used to be able to do this up to 1.3, but in 1.4 they
have tightened upthe compiler. According to http://java.sun.com/j2se/1.4/compatibility.html:>The
compiler now rejects import statements that import a type from the >unnamed namespace.
Previous versions of the compiler would accept such import >declarations, even though they
were arguably not allowed by the language >(because the type name appearing in the import
clause is not in scope). The >specification is being clarified to state clearly that you
cannot have a >simple name in an import statement, nor can you import from the unnamed
>namespace. >To summarize, the syntax >import SimpleName;>is no longer legal.
Nor is the syntax >import ClassInUnnamedNamespace.Nested;>which would import a nested
class from the unnamed namespace. To fix such >problems in your code, move all of the classes
from the unnamed namespace >into a named namespace.

--
To unsubscribe, e-mail:   <mailto:tomcat-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-dev-help@jakarta.apache.org>


Mime
View raw message