Bugzilla – Full Text Bug Listing
| Summary: | Can not find the tag library descriptor for "/WEB-INF/<tld> suddenly showing up | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [WebTools] WTP Source Editing | Reporter: | pjs38 | ||||
| Component: | jst.jsp | Assignee: | Nitin Dahyabhai <thatnitind> | ||||
| Status: | RESOLVED FIXED | QA Contact: | Nick Sandonato <nsand.dev> | ||||
| Severity: | major | ||||||
| Priority: | P3 | CC: | pjs38, rakes123, sp309v, thatnitind | ||||
| Version: | unspecified | Flags: | nsand.dev:
review+
|
||||
| Target Milestone: | 3.3.1 | ||||||
| Hardware: | Macintosh | ||||||
| OS: | Mac OS X - Carbon (unsup.) | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
pjs38
Is this a WTP project (Dynamic Web Project/EAR/...)? Or a project created by third party plug-ins? (In reply to comment #1) > Is this a WTP project (Dynamic Web Project/EAR/...)? Or a project created by > third party plug-ins? WTP. Moving to WTP What offending line? Can you attach a sample project showing the problem? (In reply to comment #4) > What offending line? Can you attach a sample project showing the problem? <%@ taglib uri="/WEB-INF/<tld>" prefix="<prefix>"%> 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? (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. 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? (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. 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. (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? Created attachment 194228 [details]
possible patch direction
Nitin, looks like a reasonable fix. I've checked in your changes. *** Bug 327409 has been marked as a duplicate of this bug. *** |