So, the problem: - I have a component let's say ActionLink in TML - I have onAction... method in the Java
The new behaviour for checking dead code, will render exception if I comment the ActionLink in TML, and I leave active the method in Java.
This is OK, but today such exception occured when I put the ActionLink inside an If. The tested object had value null, so the If did not render and so the actionlink component become non-existant and Tapestry complained with an exception that the onAction method references a component that does not exist.
This was very strange behaviour and after this I had another thing even more strange. Live reload stopped working and although I deleted both the ActionLink in the TML, and in the Java code and it was compiling OK, Tapesty still insisted on giving an ExceptionReport that the onAction method referenced an component that does not exist (except that this time, there was not a single onAction method in the class, all were deleted and recompiled). So it was obviously giving an old version, not reloading neighter TML, nor Java, despite being in development mode.
I should note that I use an ExceptionReport page, and it is a very basic one.
smime.p7s
Description: S/MIME Cryptographic Signature
