Re: JSP Bean not working
Have you considered putting Client in a package and then referencing the package? While people occasionally get away with packageless classes, it's highly recommended that all classes be in a package. --David John Byrne wrote: Hello all, I can’t get a simple form to work. The error I’m getting is: org.apache.jasper.JasperException: Unable to compile class for JSP: An error occurred at line: 8 in the jsp file: /CreateClient.jsp Client cannot be resolved to a type 5: meta http-equiv=Content-Type content=text/html; charset=utf-8 / 6: titleFormTest/title 7: /head 8: jsp:useBean id=client scope=request class=Client / 9: jsp:setProperty name=Client property=* / 10: body 11: H1Validating New User Data/H1 I’ve attached a zip file with the jsp code, html files, web.xml, classes and hierarchy in it. Help! Thank you, John John Byrne Support Network for Battered Women 1257 Tasman Dr. Suite C Sunnyvale, CA 94089 (408) 541-6100 x 138 Fax: (408) 541- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: JSP Bean not working
From: John Byrne [mailto:jby...@snbw.org] Subject: JSP Bean not working 8: jsp:useBean id=client scope=request class=Client / JSPs are not allowed to use the default (empty) package; you need to add a package statement to your Client class and include that in the JSP. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: JSP Bean not working
From: David Smith [mailto:d...@cornell.edu] Subject: Re: JSP Bean not working it's highly recommended that all classes be in a package. For JSPs, it's not just recommended, it's required by the spec. Servlets can get away with an empty package, JSPs can't. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: JSP Bean not working
Caldarale, Charles R wrote: From: David Smith [mailto:d...@cornell.edu] Subject: Re: JSP Bean not working it's highly recommended that all classes be in a package. For JSPs, it's not just recommended, it's required by the spec. Servlets can get away with an empty package, JSPs can't. I can't disagree with that. The JSP spec does indeed enforce the use of packages. My thought was more general as a practice for all java programming and probably misleading as a result. Good catch. :-) -- David - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
