- This topic has 24 replies, 5 voices, and was last updated 17 years, 8 months ago by
.
-
Posts
-
Brian,
I did quite a bit of testing using Eclipse 3.2.1 and MyEclipse 5.1 (our All-In-One installer)Here are my steps, let me know where my steps are differing from yours:
1) I create a new web project in a new workspace.
2) I created a single JSP page, with the contents as follows:<%@ page language="java" pageEncoding="ISO-8859-1"%> <%@ taglib prefix="c" uri="http://java.sun.com/jsp/jstl/core" %> <%@ taglib prefix="fmt" uri="http://java.sun.com/jsp/jstl/fmt" %> <%@ taglib prefix="fn" uri="http://java.sun.com/jsp/jstl/functions" %> <%@ taglib prefix="bean" uri="http://struts.apache.org/tags-bean" %> <%@ taglib prefix="html" uri="http://struts.apache.org/tags-html" %> <%@ taglib prefix="logic" uri="http://struts.apache.org/tags-logic" %> <%@ taglib prefix="tiles" uri="http://struts.apache.org/tags-tiles" %> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <body> <html:link action="/category" paramId="no" paramName="category" paramProperty="id" styleClass="no_line"> <c:if test="${!empty category.thumbnailImageURL}"> <html:img src="${category.thumbnailImageURL}" styleClass="photo_border_thumbnail" border="0" hspace="3" align="absmiddle" height="30" width="30" alt="${fn:escapeXml(category.name)}" /> </c:if> <c:out value="${category.name}" /> </html:link> </body> </html>3) I create a User Library with JSTL 1.1 and Struts 1.2 JARs in it, added it to my biuld path. Rebuild the project, closed and reopened the editor.
4) No warnings were marked on the tags, autocomplete and validation worked.5) I removed the user library, and instead did “Add External JAR” from the Library page of the build path properties.
6) I cleaned the project again, closed and reopened the editor.
7) Again, no warnings and autocomplete/validation worked.8) To make sure I wasn’t see a cache bug, I removed the libraries from the build path and cleaned/reopened the editor and the tags were all marked with warnings about unknown tags and no autocomplete worked.
So as of now I cannot reproduce an issue with taglibs being parsed from external JARs.
You have only used the taglibs that are showed in the preferences pannel from
MyEclipse –> J2EE Project –> Web Project –> Tag Libraries.
Those taglibs are built into myeclipse.
The problem ( with this new version is with anything besides those taglibs )
For example try repeating the process with any of these three taglibs.
sitemesh :
https://sitemesh.dev.java.net/files/documents/887/7635/sitemesh-2.2.1.jardisplaytag :
http://displaytag.sourceforge.net/m2repo/displaytag/displaytag/1.1/displaytag-1.1.jaroscache :
https://oscache.dev.java.net/files/documents/629/37840/oscache-2.3.2-full.zipI have this problem with another 4 or 5 taglibs .
Brian,
Great followup. I tried with all 3 of those, and added as “External JARs” you are right, it doesn’t work at all. But if you create a User Library out of the JARs, it does work. Maybe that workaround might help you until we get this bug fixed completely. Thank you for the help finding this, I’ll go ahead and file my findings for the dev team.I would like to update to latest version but I can’t do so if this isn’t fixed.
Has it been fixed ?
Thx
Brian
Brian,
I’m not sure if this item did get fixed in 5.5M1. However, have you considered the user-library approach to fix your problem? According to Riyad’s post you can get the JSP Editor in 5.1 to detect the jars if they are in a user-library instead of an external jar.
You can configure a user-library at:
Window > Preferences > Java > Build Path > User Libraries
Then do New… and add your external jars to this new library.
Then you can add this user-library to your project through the project properties > Build path page.The library approach is not suitable for my circumstances or those of others that I work with.
We use apache maven for build management , specifically the mvn eclipse:eclipse command in order to build our .classpath and .project files.
This is the most common means of build management these days in large enterprises , the maven pom.xml file contains a list of the project dependancies. The pom.xml file is stored in the Source Control System. This eleminates the need for each developer ( often hundreds ) to
know what the 50+ dependancies for ever project are . This approach is called build system management.This is why the user-library approach is not usefull for me or my colleagues.
But I will try getting it running again sometime in the next couple of months , untill then I’m going to stick with the MyEclipse 5.0 version.
brianofiach,
Maven support is something we are looking hard at for 5.5 and 6.0, we realize a lot of big companies are using it to keep their environments sane, and we need to support that.
