[prismmed]

I’ve added JSTL capabilities to a brand new project (Enterprise Project including Web project). When I deploy, I get most of my jars, but no jstl jars.

I have selected EE 5.0 libraries in my project settings.

I manually searched for jstl jars and found it under the C:\Program Files\MyEclipse 6.0\eclipse\plugins plugins directory (oddly when I browse to this directory I cannot see the com.genuitec.eclipse.* directories, I only found them through Windows search). I copied the jar into my WEF-INF/lib and it deployed, now I get a runtime exception about the tld not found:

“org.apache.jasper.JasperException: File “/WEB-INF/c.tld” not found”

There are no tlds in my WEB-INF directory.

Seems that MyEclipse really isn’t adding JSTL support to my project. Please help.

[Loyal Water]

Can you go to MyEclipse > Installation Summary > Installation Details and paste the information here for me.

[prismmed]

*** Date:
Thursday, February 21, 2008 10:58:38 AM EST

** System properties:
OS=WindowsXP
OS version=5.1
Java version=1.5.0_11

*** MyEclipse details:
MyEclipse Enterprise Workbench
Version: 6.0.1 GA
Build id: 6.0.1-GA-200710

*** Eclipse details:
MyEclipse Enterprise Workbench

Version: 6.0.1 GA
Build id: 6.0.1-GA-200710

Eclipse Platform

Version: 3.3.1.R33x_r20070911-_19UEkpF-B7Uh2hKy75y
Build id: M20070921-1145

Eclipse RCP

Version: 3.3.1.R33x_r20070802-8y8eE8sEV3Fz0z0GlHJrXvTAUS
Build id: M20070921-1145

Eclipse Java Development Tools

Version: 3.3.1.r331_v20070629-7o7jE72EDlXAbqAcnbmyg1rf8RIL
Build id: M20070921-1145

Eclipse Plug-in Development Environment

Version: 3.3.1.R33x_r20070802-7N7M3D1VIA_52JsDFsEC
Build id: M20070921-1145

Eclipse Project SDK

Version: 3.3.1.R33x_r20070802-7M7J78_mu1mnlRa7A4Ns52XeZ6D0
Build id: M20070921-1145

Eclipse Graphical Editing Framework

Version: 3.3.1.v20070814
Build id: 20070814-1555

Eclipse startup command=-os
win32
-ws
win32
-arch
x86
-showsplash
-launcher
C:\MyEclipse6\eclipse\eclipse.exe
-name
Eclipse
–launcher.library
C:\MyEclipse6\eclipse\plugins\org.eclipse.equinox.launcher.win32.win32.x86_1.0.1.R33x_v20070828\eclipse_1020.dll
-startup
C:\MyEclipse6\eclipse\plugins\org.eclipse.equinox.launcher_1.0.1.R33x_v20070828.jar
-exitdata
2f4_74
-vm
C:\MyEclipse6\jre\bin\javaw.exe

[prismmed]

A followup, there is one error in my original post. I found that there are 2 plugin directories, eclipse and myeclipse, so disregard that portion about not being able to browse the com.* plugins. My original problem still exists, and I’ve had to manually copy the jstl-1.2.jar into web-inf/lib

[Loyal Water]

Can you switch to a new workspace, create a new Java EE 5 Web Project and deploy it to the MyEclipse Tomcat Server. Now check if the jstl-1.2.jar got deployed. Let me know what result you get.

[prismmed]

It does indeed deploy to the default Tomcat server.

However, when configuring JBoss 4.x and deploying, it does not. The web-inf/lib is empty.

So it appears that the problem may be deployment configuration specfiic.

I would try other app servers but these are the only 2 I have.

[prismmed]

In the project wizard J2EE 1.4 is the default. If I choose “JSTL Support – Add JSTL libraries to WEB-INF/lib folder”, then it deploys to JBoss.

If I choose Java EE 5.0, whether I previously checked the JSTL Support box or not, it greys out the selection and does not deploy to JBoss, only Tomcat.

[Jon Ericson]

Hi,

Your problem is the c.tld file is not usually in the jstl-1.2.jar, but in the standard.jar. Add that to your build path and see if it works.

Why this has changed from 1.4 to EE 5 I don’t know. Good luck.

[prismmed]

True, I was porting from an old project and I had to convert all the tld references to the “http://java.sun.com…” however it should still deploy the JSTL tag library. Fixing the tld URI in the JSP page only caused the problem to change to one of not having the JAR.

So you are saying jstl is now in the standard.jar, so shouldn’t MyEclipse add the proper reference / deploy it correctly?

[Jon Ericson]

Close. Check out this answer on the bug I reported:

http://www.myeclipseide.com/PNphpBB2-viewtopic-t-20085-highlight-jstl.html

Basically, I had configured my project for Java EE 5, which by definition means these jars no longer have to be deployed with our application. Per spec, they are supposed to be handled automatically by the container (Tomcat 6, for example).

If your project is defined as Java 1.4 (and related settings in the web.xml file), then the jstl.jar and the standard.jars have to handled by the developer (such as being deployed with the application).

This is a run-time error. If you are testing your apps on Tomcat 5.5 (which is not EE 5), we get the jasper error messages such as not finding the c.tld file. Had we deployed it to an EE 5 spec container (such as Tomcat 6), we wouldn’t get these errors.

I suppose the reason the IDE can’t catch this error when deploying to an external location is that it doesn’t know what the container is… it is external, after all!

[Author]

Posts