For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub
- This topic has 17 replies, 6 voices, and was last updated 20 years, 1 month ago by
.
-
Posts
-
Hi guys,
taglib directives leads to failure(ignore) of ‘Validate JSP’ operation
I observed that if a decently long jsp page (around 150+ lines, in my case) if includes a few taglib directives, leads to the Validate JSP operation to be ignored. 👿
Select JSP file –> right click [context menu] –> Validate JSP fails.
My JSP page had the following taglib directives
<%@ taglib uri=”http://java.sun.com/jstl/core” prefix=”c”%>
<%@ taglib uri=”http://java.sun.com/jstl/session” prefix=”sess”%>
<%@ taglib uri=”http://java.sun.com/jstl/string” prefix=”str”%>
<%@ taglib uri=”http://cachatto/utility” prefix=”utility”%>
<%@ taglib uri=”http://cachatto/Parse” prefix=”parse”%>
<%@ taglib uri=”http://java.sun.com/jstl/response” prefix=”res”%>This is definitely a bug in myEclipse. The bug is probably triggered off due to the combination of the presence of many taglib directives & length of the jsp page.
I have verified that temporarily commenting out the taglib directives leads to proper functioning. However all the jsp tags are ignored. Seemingly myeclipse gets lost when it has to handle multiple taglibs.
– Deepak Kenchamba.
1) What version of Eclips are you using? (Help > About)
2) What version of MyEclipse?
3) What version of JSTL?
4) Where are you getting the following taglibs from:<%@ taglib uri=”http://java.sun.com/jstl/session” prefix=”sess”%>
<%@ taglib uri=”http://java.sun.com/jstl/string” prefix=”str”%>
<%@ taglib uri=”http://java.sun.com/jstl/response” prefix=”res”%>I have check JSTL 1.0 and 1.1 and these URIs do not exist anywhere, are these addons to the JSTL?
@support-rkalla wrote:
Matrin,
This is a quick fix, what you need is to have javac.exe in your system’s PATH environment variable, that is what MyEclipse uses to validate the JSP pages.Hello,
Thank you so much for this quick fix … i thought that i would have to wait for the next milestone release of the work bench … but this quick fix got the validation up and running .. Thanks a zillion 🙂
