to put things in perspective. it didn't get caught because the test cases are simple and do take into account this type of use. The developers have worked very hard to expose as many bugs as possible and fix them, but considering jasper2 was totally reworked to include all these features a few bugs slipped by.
Perhaps it would be better to contribute some real-world complex tag examples. This way it will make sure future releases will not contain this same bug. jasper2 is a tremendous improvement over jasper1 for extensive tag use. as others have noted, you can work around it by turning off tag pooling. peter Dave Townsend wrote: > > You have to wonder why 4.1.10 has been marked as the production release with > such an obvious bug. > > Dave > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
