Hi Matt,

The suggestion you gave is exactly what's in my JSPX page so that isn't the problem. The problem lies in the TAGX file itself. It can't find the prefix of "<jsp:doBody/>" in the TAGX file.

Any help would be nice.
Thanks,
Vinu.

By the way Matt, your blog is one of the best I've ever seen.

Raible, Matt wrote:
Maybe this will help:

<tags:xhtmlbasic xmlns:tags="urn:jsptagdir:/WEB-INF/tags"
                 xmlns:jsp="http://java.sun.com/JSP/Page";
                 xmlns:fmt="http://java.sun.com/jstl/fmt_rt";
                 xmlns="http://www.w3.org/1999/xhtml";>
  <jsp:directive.page contentType="text/html" />


-----Original Message----- From: Ammai.com [mailto:[EMAIL PROTECTED] Sent: Friday, July 18, 2003 12:12 PM To: [EMAIL PROTECTED] Subject: Tomcat 5.0 w/ JSPX and TAGX


Hi there,


I'm using Tomcat 5.0.4 and I think it is the best Tomcat release to date. Everything works fine and it seems faster than the 4.x series.

Anyways, I was testing JSP 2.0 by writing a sample JSP Document (JSPX) and everything worked fine. Then I tried to use a tag file by writing a "xhtmlstrict.tag" file and used it in the JSPX document and everything worked fine again. However, if I change the extension of the .tag to .tagx (so that it is a Tag XML document, just like JSP XML document), Tomcat's giving an exception:

org.apache.jasper.JasperException: null(4,-1) Undeclared prefix in name: "jsp:doBody".

This is what's in the "xhtmlstrict.tagx" file:

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
                "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>
<html xmlns="http://www.w3.org/1999/xhtml"; xml:lang="en" lang="en">
        <jsp:doBody/>
</html>

It seems like Tomcat isn't recognizing the "jsp" prefix. Is there any way to fix that?

Thanks,
Vinu.



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



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



Reply via email to