You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2001/09/18 05:35:43 UTC
DO NOT REPLY [Bug 3668] New: -
Validation error reporting
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3668>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3668
Summary: Validation error reporting
Product: Tomcat 4
Version: 4.0 Release Candidate 2
Platform: All
OS/Version: All
Status: NEW
Severity: Major
Priority: Other
Component: Jasper
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: hans@gefionsoftware.com
Jasper does not create jsp:id attributes for custom actions in the XML View of
the document passed to a TagLibraryValidator. Errors found by a validator can
therefore not be associated to the location of the error in the JSP page source.
The spec does not require the use of the jsp:id attribute, but considering that
Jasper is the Reference Implementation, I feel that it really should.
Also, Jasper reports all types of validation errors (found by Jasper itself or
by a validator) with a full stack trace. Considering that the stack trace does
not provide any useful information in this case, and that the error message is
targeted to non-programmers ("page authors"), I suggest that only the validation
error message is displayed for validation errors.