[Paolo Denti]

i really cannot understand if the problem is with my code or with myeclipse (5.1 + eclipse 3.2.1)

in the following code for example (but in every page with code nested if tags like in this case)

<%@ taglib prefix="c" uri="http://java.sun.com/jsp/jstl/core" %>
...
<a href="<c:url value="/test.htm"/>"<c:if test="${param.currentLeft == 'show'}"> class="current"</c:if>>txt txt txt</a></li>

i get the following warning: Undefined attribute name (<c:if test=”${param.currentLeft == ‘show’}”> class=”current”</c:if>)”

the problem (if it is really a myeclipse problem …) is not blocking but it is very annoying
any idea ?
thanks

[CGIFederal]

You could move your c:if tag to inside the class=”” attribute.

<a href=”<c:url value=”/test.htm”/>” class=”<c:if test=”${param.currentLeft == ‘show’}”>current</c:if>”>txt txt txt</a></li>

[Paolo Denti]

@Mike.Kearns wrote:

You could move your c:if tag to inside the class=”” attribute.

<a href=”<c:url value=”/test.htm”/>” class=”<c:if test=”${param.currentLeft == ‘show’}”>current</c:if>”>txt txt txt</a></li>

thanks !
your tip in fact eliminates the warning even if the generated html is different (same visual result but bigger than the original)
<a href=”/test.htm” class=””>txt txt txt</a>
vs
<a href=”/test.htm”>txt txt txt</a>

[Paolo Denti]

btw i think that the problem lies in the myeclipse “html validator”

[Paolo Denti]

any news from the myeclipse team ?

[Greg]

The HTML validator is from the WTP platform. However, with MyEclipse we give you the ability to disable the HTML validation for that particular file if it is causing a problem. Just right-click the project and go to MyEclipse > Validation > Excluded Resources and you can select your JSP file.

[Paolo Denti]

@support-greg wrote:

The HTML validator is from the WTP platform.

thx Greg, i already did it but it is not a nice solution if i want to develop an xhtml compliant webapp.
btw i understand now that it not a myeclipse problem and i will try to submit a bug to the eclipse team (it still looks a bug to me …)

[jieryn]

If you check this thread it sure seems like an acknowledgement that it is a bug with MyEclipse. Like the original poster, I don’t feel disabling validation on literally every single .jsp resource is viable; Validation has saved me in the past, I don’t want to disable it.

Any projection for when this will be fixed? Thanks! 🙂

[Riyad Kalla]

No ETA for a fix just yet, but the JSP lexer has some TODO items for our 5.5 and 6.0 releases to make it smarter about allowable JSP constructs (possibly the most complex language ever 🙁

[Paolo Denti]

@jieryn wrote:

If you check this thread it sure seems like an acknowledgement that it is a bug with MyEclipse.

therefore i posted a wrong bug to the bugzilla eclipse team ?

[Riyad Kalla]

paolo,
Both places are valid. It depends which team tackles it first. If we fix the bug first we’ll commit the fix back to the WTP team and visa versa.

[Author]

Posts