Community
Participate
Working Groups
For custom tags, having an end tag without a start tag doesn't cause a validation message. As this can cause a translation failure, it should.
Actually, it should cause a validation message in the unbalanced tag. An unbalanced '{' or '}' syntax error is nearly impossible to figure out when it doesn't original from the user's own scriptlets.
Fixed.
Verified in 3.1M3-20081107075001. Should the severity of this be controllable via the JSP Validation preferences?
Technically the MarkupValidator lives in XML. Creating preferences for that would lend weight to the idea suggested in bug 254647 comment 2, although the validator would have to become headless and registered with the validation framework to really have that make sense.