[Jon Ericson]

When trying to access a .jsp after deployment, I’m getting the following error to my browser:

JasperException: The absolute uri: http://java.sun.com/jsp/jstl/core cannot be resolved in either web.xml or the jar files deployed with this application.

I have determined that the jstl-1.2.jar is not being placed in the .war file on deployment. When looking at the libraries on the java build path (properties -> Java Build Path -> Libraries) I see that the jars are defined slightly differently in 6.0 than 5.1.

Note: I have just installed a new version of MyEclipse Enterprise Workbench 6.0 over a new, clean workspace. Previously I have been using MyEclipse Enterprise Workbench 5.1.

On MEW 5.1, the .jar is defined as an external .jar. That deploys.
On MEW 5.1, I remember clicking a button to add the jstl libraries.
On MEW 6.0, the jstl-1.2.jar was “predefined” as part of the Java EE 5 libraries, none of which are being sent to the .war file.
On MEW 6.0, when I select Java EE 5, there is no button to add the jstl libraries.

Soooo… My question is: [Why does the jstl-1.2.jar not deploy? Any .jars defined as “external jars” are deployed just fine, but none of the jars in the Java EE 5 predefined library. Is that a bug, or do I just not understand the libraries tab? (I have scanned this forum and the help, but cannot find the answer).

—-
My installation:
OS=WindowsXP
OS version=5.1
Java version 1.5.0_11

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

( etc )

[Loyal Water]

Can you switch to a new workspace, create a new JAVA EE 5.0 web project and deploy it to tomcat. Next, go to WEB-INF/Lib folder and check if the jstl-1.2 jar is there.

I was able to successfully deploy the project with the jstl-1.2 jar. Let me know what result you get.

[Jon Ericson]

Hello Nipun,

I did what you said, and the JSTL libraries still did not deploy with the project. Here is what I did.

1. Created new workspace.
2. Create new project
File -> New -> Project
Project Name: nipun
Java Specification Level: Java EE 5.0
Everything else was defaulted.
Note: When I clicked on the Java Specification Level EE 5.0, the JSTL support options became display only.

3. Create new deployment (menu button)
Server: <Externally Launched>
Deploy Type: Packaged
War file deployed to Webapps directory.

4. Start Tomcat. Application deployed, directories created.

5. WEB-INF/lib folder is completely empty.

In other words, the problem was replicated and remains.

[Loyal Water]

I just noticed that you are deploying the application to an externally launched server. Can you configure the Tomcat Connector and launch the server from within MyEclipse and test this out again. You can try deploying to the MyEclipse Tomcat server and check if the jar is getting deployed. Let me know what result you get.

[prismmed]

I have the same problem, I see there was no followup on this. A new EE 5.0 does not deploy jstl libraries in my war

[Jon Ericson]

Nipun,

Deploying to a .war file in an externally launched server should make no difference. The .jar files should deploy to the .war file.

[Loyal Water]

OneMist8k,
I know deploying to an externally launched server should make no difference but I would still like you to test the deployment against the MyEclipse Tomcat server. It would help us eliminate the option of the issue being related to your Tomcat Server.

[Riyad Kalla]

OneMist8k,
The reason you are seeing the behavior you are is because JSTL 1.2 is part of the Java EE 5 spec. So if you are deploying to a spec compliant application server, it already provides those libraries for you (it’s similar to the reason why we don’t deploy servlet.jar or JSF JARs to Java EE 5 servers, it’s all provided by the server.

[Author]

Posts