Community
Participate
Working Groups
Suppose you have a Dynamic Web Project with two folders mapped in the Web Deployment Assembly page (WebContent and WebContent2). Suppose you have taglib1.tld in WebContent/taglib/ and taglib2.tld in WebContent2/taglib/. Now suppose your web.xml (in WebContent/WEB-INF) says the following: <jsp-config> <taglib> <taglib-uri>http://uri1</taglib-uri> <taglib-location>/taglib/taglib1.tld</taglib-location> </taglib> <taglib> <taglib-uri>http://uri2</taglib-uri> <taglib-location>/taglib/taglib2.tld</taglib-location> </taglib> </jsp-config> Then, try to write a JSP in WebContent/ with the following: <%@ taglib prefix="taglib1" uri="http://uri1" %> <%@ taglib prefix="taglib2" uri="http://uri2" %> The JSP editor returns an error on the second line, saying: Can not find the tag library descriptor for "http://uri2" However, it should be able to correctly find the tld for both the URIs, since they are in two web application deployed folders, although the second one is in a folder different from that of web.xml and the JSP. I'm going to attach a ZIP containing a project that shows this problem.
Created attachment 182691 [details] ZIP file containing a project that shows the problem
I am looking into Bug 229760 which is in similar area.I will look into this problem.
Created attachment 182793 [details] patch Resolving path with the help of FacetModuleCoreSupport.
Patch looks good. Thanks, Rakesh.
has this patch been tested for jsp tag files (in /WEB-INF/tags). the bug description and discussion concerns only TLD files.
(In reply to comment #5) > has this patch been tested for jsp tag files (in /WEB-INF/tags). the bug > description and discussion concerns only TLD files. Sorry, I haven't tested yet, however this should be in WTP 3.2.3 (Helios SR2), released some days ago, so you may try and let us know.
For me, the fix is ok (I verified it with my use case).
yes. it works in a simple test case, but doesn't work for me in reality. my projects were created many many moons (literally because of the eclipse version naming ;-) ago and possibly there's some version number that's keeping this from working. thanks for your help. if i figure this out i'll post back.
I would suggest you to create an empty new workspace and import your projects in the new workspace. In this way your should have a clean environment to test with. If the problem still occurs, the best would be to find out a simple test case to attach here or (even better) in a new bug report. Note: in my tests, I saw that, after opening a JSP which showed the red marker on the taglib directive before the fix, I had to press the right mouse button on the editor and choose "Validate" in order to make sure that the error and warning markers were refreshed. In this way, the red marker on the taglib directive correctly disappeared.
(In reply to comment #9) > I would suggest you to create an empty new workspace and import your projects > in the new workspace. In this way your should have a clean environment to test > with. If the problem still occurs, the best would be to find out a simple test > case to attach here or (even better) in a new bug report. > > Note: in my tests, I saw that, after opening a JSP which showed the red marker > on the taglib directive before the fix, I had to press the right mouse button > on the editor and choose "Validate" in order to make sure that the error and > warning markers were refreshed. In this way, the red marker on the taglib > directive correctly disappeared. Clearing the .metadata/.plugins/org.eclipse.jst.jsp.core/taglibindex directory in the existing workspace, while Eclipse is _not_ running, will do just as well.
(In reply to comment #10) Oh, as should closing and reopening your projects, at lest the ones with the tag libraries in them.
i have a test case that isn't working. it's a tar.gz of a workspace I just created with a project not working. there are two "deployment assemblies" /web and /built/web /built/web/WEB-INF/tags contains foo.tag /web/departmentGroup/addEdit/addEditForm.jsp contains a reference to the tag which cannot be resolved (in fact the directory /WEB-INF/tags is red). There's also a Test.java for good measure ;-) I'll attach in a sec...
Created attachment 190201 [details] project demonstrating failure to resolve jsp tag files i tried to attach a workspace but it's too large. i believe this project can be imported into a fresh workspace and it'll show the problem.
Opened bug 338751 specifically for tag file case. David, your example project was VERY helpful in tracking it down.
