DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=19491>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=19491 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID ------- Additional Comments From [EMAIL PROTECTED] 2005-07-25 01:13 ------- The root cause of the problem is the use of scriptlets. If the impact of the scriptlets is to place a tag inside a code block of which Jasper is not aware then the variable scoping is going to get messed up. I think you test case only works for the non-pooled configuration due to another bug that has since been fixed. The correct way to do this is to use the conditional tags from the JSTL tag library. This way, Jasper knows about the extra code blocks and correctly scopes the scripting variables. A simpler version of your test case works correctly (latest version from CVS) for pooled and non-pooled configurations using the JSTL taglib. Using scriptlets, an exception is thrown for both pooled and non-pooled. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
