https://bz.apache.org/bugzilla/show_bug.cgi?id=70010
--- Comment #2 from linguini <[email protected]> --- Hi, thanks for the reply, understand the usefulness of try/finally is to make sure to always accessing releaseTags at the end, but there can be many ways addressing this. Release tags can be handled at a different position, for example the Page scope, at the and of the generated page. By the way, about pooling, at the end it's the idea of using reuse(), and guaranteed to be released after all, then the approach for this can be conditionally generate the block by enablePooling flag and our release notes should address it well on the bytecode increase/decrease when the param is turned on/off. I address this because there are many legacy projects out there are having large jsp files with customized tags, migrating the whole jsp file will take more risks than can call a "trade-off". I do expect we have a proper way for this issue and an option offer for legacy ones would be a wonderful contribution. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
