Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
5.1.0.0, 5.0.18
-
None
Description
The failures are due to an incorrect error message generated by org.apache.tapestry5.ioc.internal.util.OneShotLock
As mentioned in the comments of that method, Thread.currentThread().getStackTrace[4] is used instead of
Thread.currentThread().getStackTrace[3] and this was found by trial and error... in java1.6 however,
Thread.currentThread().getStackTrace[3] is indeed the correct choice for the caller method