Folks, A correction on the cause of the bug. If a JSP defines a prefix with the same name as a literal HTML-tag like html, body, head, etc.,you'll run into this problem. E.G: <%@ taglib uri="/WEB-INF/struts-html.tld" prefix="html" %> <html> ... </html> Since the code in the JSP is case sensitive, changing the case of the literal HTML-tags (or the prefixes) already solves the problem: <%@ taglib uri="/WEB-INF/struts-html.tld" prefix="html" %> <HTML> ... </HTML> So no need to put <html:html>...</html:html> in your JSP's. Sorry for the confusion. Raymond P. Brandon ------------------------------------------------------------------------ Software Engineer Compuware Europe BV Product Development Hoogoorddreef 5 Uniface Technology P.O.Box 12933 Mailto:[EMAIL PROTECTED] 1100 AX Amsterdam The Netherlands Tel: +31 - 20 - 3126510 Fax: +31 - 20 - 3116364 > Initializing configuration from resource path /WEB-INF/struts-config.xml > [20/Jun/2001 11:33:22:2] info: action: Looking for > Action instance for > class OrderSample.web.MyOrderSetProfileAction > [20/Jun/2001 11:33:22:2] info: action: > Double checking for Action instance already there > [20/Jun/2001 11:33:22:2] info: action: Creating new Action instance > [20/Jun/2001 11:33:22:2] info: > [20/Jun/2001 11:33:28:7] error: Exception: SERVLET-compile_failed: > Failed in compiling template: /web/MyOrderQuery.jsp, JSP Error: > Class was not found for :html > Exception Stack Trace: > java.lang.Exception: JSP Error: Class was not found for :html > at com.netscape.jsp.JSP.addTagdata(Unknown Source) > at com.netscape.jsp.JSP.parseUserTag(Unknown Source) > at com.netscape.jsp.JSP.parseTag(Unknown Source) > at com.netscape.jsp.JSP.parseNext(Unknown Source) > at com.netscape.jsp.JSP.parseBlock(Unknown Source) > at com.netscape.jsp.JSP.parse(Unknown Source) > at com.netscape.jsp.JSP.compile(Unknown Source) > at com.netscape.server.servlet.jsp.JSPCompiler.JSPtoJava(Unknown Source) > ... etc.
