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=4941>. 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=4941 appearence of taglib directive after the usage of tag/prefix should result in fatal error. [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |LATER ------- Additional Comments From [EMAIL PROTECTED] 2001-12-05 16:32 ------- This bug is actually quite hard to fix with the current structure of Jasper. Jasper currently treats an undeclared custom tag as an uninterpreted tag. Not only is the error not detected, but no code is generated for the tag. A proper fix requires a multi-pass compiler to scan all taglib directives before processing tags. A multi-pass compiler is planned for a future release. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
