https://bz.apache.org/bugzilla/show_bug.cgi?id=65124
--- Comment #17 from John Engebretson <jeng...@amazon.com> --- Our Tomcat8 implementation modified Generator.java along the following lines: 1. When a tag call is found (any tag!): - generate a method name that uniquely identifies the tag class and the provided attributes - add the name/details to a list - generate code that calls the named method 2. Near the end of the file (after all calls are processed): - iterate through the loop - generate each method The sample code attachment includes the method generateOptimizedTagCall(). Let me know if you'd like to see more snippets... sorry, I know it's hard to read only pieces of the whole. The end result is that all JSPs everywhere become smaller, with zero application change or even activation required. I only see disadvantages with a tag-specific, application-specific solution. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
