I am definitely willing to put in time to test the patches. The
discussion has been great and covered all the concerns I had. With the
test pages I have, the 64K limitation forces me to break long pages into
several jsp files using both include directive and action include. In my
mind, it's good
18:59:14 -0400 (EDT)
> From: Denis Benoit <[EMAIL PROTECTED]>
> Subject: Re: [PROPOSAL] Tag pooling/reuse in Jasper 2
> To: Tomcat Developers List <[EMAIL PROTECTED]>, Jan Luehe
<[EMAIL PROTECTED]>
> MIME-version: 1.0
> Delivered-to: mailing list [EMAIL PROTECTED]
Hi,
For my part, I'm a little concerned about the second approach. If there is
a lot of pages with a lot of distinct tags; tags libraries are catching on
fast; there may be a problem where Jasper would cache a lot of tags. If there
is a sudden burst of use of a given page, the stacks of the tag
Kin-Man and I have been throwing around some ideas of how to support
tag pooling and reuse in Jasper 2.
According to the spec, only tags with the same set of attributes may
be reused (see JSP.10.1.1, p.163, "Lifecycle" section, item 3):
[3] Note that since there are no guarantees on the state
