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

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

 

- Konstantin

 


From: wtp-dev-bounces@xxxxxxxxxxx [mailto:wtp-dev-bounces@xxxxxxxxxxx] On Behalf Of David Klein
Sent: Friday, March 03, 2006 12:15 PM
To: General discussion of project-wide or architectural issues.
Subject: [wtp-dev] JSP validation and runtime provided Tag Libraries

 


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.

Thanks,

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

_______________________________________________________________________
Notice:  This email message, together with any attachments, may contain
information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated
entities,  that may be confidential,  proprietary,  copyrighted  and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.

Back to the top