For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub
- This topic has 7 replies, 2 voices, and was last updated 21 years, 1 month ago by
.
-
Posts
-
MOVED FROM Installation, Configuration & Updates
==
I have checked the previous “JSP editor-unknown tags” topic and have not found a solution.
I am working on the WebWorks2 example from their website: http://www.opensymphony.com/webwork/wikidocs/TutorialLesson03.html.I have their jar, webwork-2.1.7.jar, loaded as an external jar. It contains the META-INF package containing the MANIFEST.MF file and the taglib.tld file. I have my project properties set as: MyEclipse-Web/Deployment/Library Deployment Policies/{Jars on Web Project build-path, Jars in Web Project’s user libraries}
So my jsp file:
Code:
<%@ taglib uri=”webwork” prefix=”ww” %>
<html>
<head>
<title>WebWork Tutorial – Lesson 3 – Example 1</title>
</head>
<body> <<ww:property value=”hello” />
</body>
</html>works fine when it is deployed to Tomcat, but it still shows errors of:
Code:
Unable to read TLD “META-INF/taglib.tld” from JAR file “file:C:/Dev/Eclipse-All/Eclipse301/eclipse/workspace/TestWebWork2/WebRoot/WEB-INF/lib/webwork-2.1.7.jar”: java.util.zip.ZipException: The system cannot find the file specified. NOTE: No JSP line number was avaliable so line 1 was used for the marker.
on the top line
and
Code:
Multiple annotations found at this line:
– No tag “property” defined in tag library imprted wtih prefix “ww”
– Unknown tag (ww:property).
on the line using the ww:property tag.So, how do i resolve compilation issues where it may be looking for the tld file in the webrootdir/META-INF directory when it actually exists in an external jar? Or is that even the problem?
thx
I’m using 3.8.3 in eclipse 3.0.1
– System Setup ——————————-
Operating System and version: xp
Eclipse version: 3.0.1
Eclipse build id: eclipse.buildId=M200409161125
Fresh Eclipse install (y/n): n
If not, was it upgraded to its current version using the update manager? y
Other installed external plugins: n
Number of plugins in the <eclipse>/plugins directory that begin with org.eclipse.pde.*: 8
MyEclipse version: 3.8.3
Eclipse JDK version:
Application Server JDK version:
Are there any exceptions in the Eclipse log file? Unable to open library stream for TLD: webworkI have the same setup as you, went to opensymphony and grabbed the webwork JAR file, created a new Web project, dropped just the JAR into the /lib dir, let MyEclipse automount it, then I created a new JSP page with the following content:
<%@ page language="java" import="java.util.*" %> <%@ taglib uri="webwork" prefix="w" %> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <title>My JSP 'MyJsp.jsp' starting page</title> </head> <body> This is my JSP page. <br> <w:action name="blarg" /> </body> </html>And everything worked fine. Then I removed the lib from build path and “Add External JAR” and pointed at a copy of it on my desktop, then I rebuilt the project and it still worked fine.
Maybe the JAR file is corrupt that you downloaded?
Yours probably works because you didn’t blow away your tomcat/work directory that had the jar file that you stuck in the WEB-INF/lib dir and subsequently removed from your environment .
From a clean install of eclipse301 and myeclipse383 it still doesn’t work.
Sorry, please delete that last embarrassing thought, it has been a long day and i’ve been trying everything that i can thing of, so my brain is fried.
Jeff,
I would suggest the following (I know that feeling of wanting to rip hair out/cry and smash the computer).Try and create a brand new Web Project, drop the Webwork JAR into the lib dir, let MyEclipse automount it then create a new JSP file and paste the contents I gave above, save it… did it work? If no, and you wanted to try it, I’d be happy to look at a project if you wanted to post a Zip of it online and see what might be wrong with it. The longer something takes to troubleshoot, the smaller the fix is… so I imagine restarting Eclipse with -clean or creating a new workspace would fix the problem (equivalent to a reinstall). But I think we tried that already?
All i needed to do was to drop the jar into WEB-INF/lib, like you said, and then remove it. Is that a flaw that will be fixed?
All i needed to do was to drop the jar into WEB-INF/lib, like you said, and then remove it. Is that a flaw that will be fixed?
1) I’m glad its fixed, although if you restart it may stop working, can you try this?
2) It seems external JARs are not parsed the same, let me check on this and see what is going on.#2) I checked on this with a dev and it seems that external JARs cannot currently be treated the same as JARs contained within the workbench, the reason for this has to do with the Eclipse API (IResource or something). So the workaround is to not use an external JAR and be sure to use a JAR that within the workbench somewhere.
