Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [wtp-dev] JSP validation and runtime provided Tag Libraries

> David Klein wrote:
>> I have noticed that tag libraries that are copied into a web app's
>> WEB-INF/lib directory are recognized by the JSP validator, but tag
>> libraries that are not in WEB-INF/lib, but instead on the project's
>> classpath are not recognized. By "not recognized" I mean a JSP file >> using tags from the library has these tags flagged with an "Unknown tag"
>> error.  If it is perhaps a performance issue to have to search all
>> libraries on a project's classpath for TLD files, is there (or could >> there be) a means of registering such tag libraries such that they can
>> be found by the JSP validator?  A runtime that provides certain tag
>> libraries (JSTL, JSF,...) as part of the runtime would typically (I
>> believe) contribute these libraries as part of the runtime specific
>> classpath container (for which WTP has a mechanism for updating the
>> classpath when the target runtime is switched on a project).
>>
>> Let me know if there is a solution for this that I am unaware of. If
>> not, I will open a defect.

Konstantin Komissarchik wrote:
This sounds like https://bugs.eclipse.org/bugs/show_bug.cgi?id=128906, although it could be a somewhat different issue.


David,
Since the .jar file won't be within the web application at runtime, the .jar file can't be referred to directly. The TLD file inside must expose a URI using the "uri" element and the .jsp file has to use that URI to find it (assuming I'm not misreading the specs and your original posting). How is the .jsp referring to those tag libraries?

It almost sounds more like bug 129112.

https://bugs.eclipse.org/bugs/show_bug.cgi?id=129112
https://bugs.eclipse.org/bugs/show_bug.cgi?id=128906#c6

---
Nitin



Back to the top