Thiago H. de Paula Figueiredo: -1 (binding)
I don't want to be a killjoy, but I've just noticed that there's a very
nasty Tapestry DOM bug not fixed yet:
https://issues.apache.org/jira/browse/TAP5-953. Besides rendering the same
element twice in different places, it can also lead to a memory leak that
very quickly (i.e. a couple minutes) eats all the RAM and virtual memory
available. Somehow I thought it was already fixed, but it seems it isn't
yet. I reproduce it in 5.1.0.4 and it seems to still happen in 5.2 and
5.3. I'm facing it this very moment and it's maddening and time-wasting. I
work in some projects that use Tapestry DOM rewriting a lot.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
