Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 323421 - Can not find the tag library descriptor for "/WEB-INF/<tld> suddenly showing up
Summary: Can not find the tag library descriptor for "/WEB-INF/<tld> suddenly showing up
Status: RESOLVED FIXED
Alias: None
Product: WTP Source Editing
Classification: WebTools
Component: jst.jsp (show other bugs)
Version: unspecified   Edit
Hardware: Macintosh Mac OS X - Carbon (unsup.)
: P3 major (vote)
Target Milestone: 3.3.1   Edit
Assignee: Nitin Dahyabhai CLA
QA Contact: Nick Sandonato CLA
URL:
Whiteboard:
Keywords:
: 327409 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-08-23 14:14 EDT by pjs38 CLA
Modified: 2011-08-22 17:20 EDT (History)
4 users (show)

See Also:
nsand.dev: review+


Attachments
possible patch direction (3.48 KB, patch)
2011-04-27 23:57 EDT, Nitin Dahyabhai CLA
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description pjs38 CLA 2010-08-23 14:14:32 EDT
Build Identifier: 20100617-1415

Goes away as soon as I cut then re-paste the offending line (exactly as it was before).  I made no changes to the tld file.  Happened when project was imported from a Linux box.


Reproducible: Sometimes
Comment 1 Prakash Rangaraj CLA 2010-08-24 00:37:52 EDT
Is this a WTP project (Dynamic Web Project/EAR/...)? Or a project created by third party plug-ins?
Comment 2 pjs38 CLA 2010-08-24 01:30:56 EDT
(In reply to comment #1)
> Is this a WTP project (Dynamic Web Project/EAR/...)? Or a project created by
> third party plug-ins?

WTP.
Comment 3 Prakash Rangaraj CLA 2010-08-24 01:34:01 EDT
Moving to WTP
Comment 4 Nitin Dahyabhai CLA 2010-08-24 02:31:10 EDT
What offending line?  Can you attach a sample project showing the problem?
Comment 5 pjs38 CLA 2010-08-24 02:46:10 EDT
(In reply to comment #4)
> What offending line?  Can you attach a sample project showing the problem?

<%@ taglib uri="/WEB-INF/<tld>" prefix="<prefix>"%>
Comment 6 Nitin Dahyabhai CLA 2010-08-24 02:53:44 EDT
Maybe there's some detail in comment 0 I'm not understanding, but it sounds like a correct message: the exact value you used for the URI does not resolve to a tag library descriptor (tld) file (or entry in a jar).  Should it resolve?
Comment 7 pjs38 CLA 2010-08-24 02:58:00 EDT
(In reply to comment #6)
> Maybe there's some detail in comment 0 I'm not understanding, but it sounds
> like a correct message: the exact value you used for the URI does not resolve
> to a tag library descriptor (tld) file (or entry in a jar).  Should it resolve?

it should resolve.  if i cut the line and then paste it right back in, the error message goes away immediately.
Comment 8 Nick Sandonato CLA 2010-08-24 09:48:49 EDT
Is the only issue the validation message? Are you losing function like not being able to get content assist for any custom tags added by that library or anything?
Comment 9 pjs38 CLA 2010-08-24 13:31:32 EDT
(In reply to comment #8)
> Is the only issue the validation message? Are you losing function like not
> being able to get content assist for any custom tags added by that library or
> anything?

yep, that's the extent of the damage.  only some libraries are affected, even though all follow the same xml formatting.  most recently, this happened when i opened a linux eclipse project in a mac environment, but it's happened previously without an obvious trigger.  thanks.
Comment 10 Rakesh CLA 2010-11-12 00:25:37 EST
Hi Nick, isn't this the expected behavior ?
This error is reported by NamespaceValidator. As soon as we cut the for ex 
"<%@ taglib prefix="localtags" tagdir="/WEB-INF/tags" %>" , there is no way of knowing that localtags is associated with any tld.
Comment 11 Nitin Dahyabhai CLA 2010-11-12 10:29:46 EST
(In reply to comment #10)
> Hi Nick, isn't this the expected behavior ?
> This error is reported by NamespaceValidator. As soon as we cut the for ex 
> "<%@ taglib prefix="localtags" tagdir="/WEB-INF/tags" %>" , there is no way of
> knowing that localtags is associated with any tld.

Yes, but then we'd get a message about the tag itself.  The summary message is reported against taglib directives whose uri/tagdir can not be found by the JSPDirectiveValidator.  It could be a timing (and thus hard to fix) issue between when the TaglibIndex was notified of the addition of the tags folder/file and when validation was performed on the file originally.

Is /WEB-INF/<tld> the literal text of the error?
Comment 12 Nitin Dahyabhai CLA 2011-04-27 23:57:18 EDT
Created attachment 194228 [details]
possible patch direction
Comment 13 Nick Sandonato CLA 2011-07-08 15:30:40 EDT
Nitin, looks like a reasonable fix. I've checked in your changes.
Comment 14 Nick Sandonato CLA 2011-08-22 17:20:09 EDT
*** Bug 327409 has been marked as a duplicate of this bug. ***