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=10714>. 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=10714 JSP does not compile if useBean tag refers to bean w/o package name in WEB-INF/classes ------- Additional Comments From [EMAIL PROTECTED] 2002-07-11 22:24 ------- This is not a very intuitive workaround. I doubt it that a beginner user who finds that the bean that they tried to use is not available, and who understands the nature of the problem will be able to figure out that adding an import statement would going to fix it. I think it's worth addressing this because it raises the bar of entry for the technology and I have seen people being stumped by this issue several times. I looked at the spec and it doesn't say anything explicit about package names for Beans, though of course all the examples of beans have fully qualified names in them. It could be argued that this could be resolved by simply clarifying the spec, but it seems like a backwards argument to me: it's an argument on how the JSP should behave on the basis of the default behaviour of servlets. But the intended audience of JSP includes page authors who are not necessarily familiar with servlets. I think it would be equally valid to argue that the JSP classloader should resolve this type of situation. Also, clarifying it at the level of the spec won't help beginner web tier programmers, who typically won't read the spec. I guess the current behaviour of Tomcat is spec compliant anyway, and I'll take this to JSR 152. Ana -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>