facebook

JSTL treated as normal TLD

  1. MyEclipse Archived
  2.  > 
  3. Bugs
Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #200181 Reply

    JSTL is built into J2EE 1.4. A JSP that uses it references a set of formal URIs in the form:
    <%@ taglib prefix=”c” uri=”http://java.sun.com/jsp/jstl/core&#8221; %>
    The Sun documentation (http://java.sun.com/j2ee/1.4/docs/tutorial/doc/JSTL3.html) notes:
    “In the J2EE 1.4 Application Server, these are distributed in the archive <J2EE_HOME>/lib/appserv-jstl.jar. This library is automatically loaded into the classpath of all Web applications running on the J2EE application server, so it does not need be added to Web applications. ”
    However, when the taglib statement is processed by 3.6.3 on 3.0 M4 it generates an error:
    “could not load TLD for uri=http://java.sun.com/jsp/jstl/core, url=c:/workspace/yalecas/webhttp://java.sun.com/jsp/jstl/core”

    It is necessary to recognize cannonical URIs and not go looking for the TLD. The TLD is implicit in the Classpath, not part of the project. Although this example compiles with errors, it deploys and runs correctly in Tomcat where the JSP compiler doesn’t try to find the TLD in the wrong place.

    OS: Windows XP Pro, JDK: 1.4.2_02, fresh install for MyEclipse, Tomcat 4.1.24.

    #200184 Reply

    support-michael
    Keymaster

    MyEclipse JSP tools are still at J2EE 1.3 spec level (see the new Web Project wizard). So some of the new Servlet 2.4/JSP 2.0 features are not yet supported. We are revamping our tooling to support J2EE.14 in the very near future. Since JSTL is not a part of the J2EE1.3 spec it is my understanding that a webapp should package the jstl TLDs and jar files for portability.

    I was confused by your discussion of J2EE 1.4 and claim that Tomcat 4.1.29 supports JSTL since it is a J2EE1.3 web container. Have you modified Tomcat4.1 in someway to implicitly provide JSTL support to all webapps or maybe I’m just missing something here (help me understand?). Also I checked the standard1.0 c.tld uri and it should be

    <%@ taglib prefix=”c” uri=”http://java.sun.com/jstl/core&#8221; %>

    Lastly I tried simple webapp examples that assume the container will provide the JSTL 1.0 TDLs and jars with no success. So how is your env. setup to make this go?

    Regards,

    Michael
    MyEclipse Support

Viewing 2 posts - 1 through 2 (of 2 total)
Reply To: JSTL treated as normal TLD

You must be logged in to post in the forum log in