Skip to main content

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


Nitin and Konstantin,

Thanks for the information on this.  From what you replied, it definitely seemed like this scenario should be working.  So, I retried with the latest M5 build, and was glad to find out it indeed works!  What was tripping me up is the following other bug:  It had been the case in the past that the JSP validation would kick in when the JSP file itself changed, so I was used to touching and resaving the file in the editor to force a revalidation.  For some reason now, this no longer works.  So, when I created my test project, I initially did so without the tag libraries, which yielded an expected Unknown tag warning in the JSP file's editor window.  I then added the tag libraries to the project classpath, touched and resaved the JSP file in the editor, but... still had the Unknown tag warning.  Turns out I had to close the JSP editor window, and re-open the JSP file in the editor to get the validator to kick in and remove the warning.  Perhaps this is a bug with the validation framework?

Thanks,

David Klein
IBM WebSphere Everyplace Deployment Development
Austin, TX
T/L 678-9420  External: (512)838-9420
Internet: kleind@xxxxxxxxxx

----- Forwarded by David Klein/Austin/IBM on 03/07/2006 05:40 PM -----
Nitin Dahyabhai <nitind@xxxxxxxxx>
Sent by: wtp-dev-bounces@xxxxxxxxxxx

03/07/2006 03:06 AM

Please respond to
"General discussion of project-wide or architectural issues." <wtp-dev@xxxxxxxxxxx>

To
"General discussion of project-wide or architectural issues." <wtp-dev@xxxxxxxxxxx>
cc
Subject
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

_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev

Back to the top