> 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.
Yes, that's the right explanation. There's unfortunately no good test suite for Jasper, as Watchdog just doesn't test this. > Perhaps it would be better to contribute some real-world complex tag > examples. Yes, please do ! > 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. The code generator generates much more optimized code, and is therefore more complex. > as others have noted, you can work around it by turning off tag pooling. Nice workaround :) I'll mention it. Remy -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
