This issue is described here: https://issues.apache.org/jira/browse/TAP5-1208
The trouble isn't with your JRE but with how tapestry rewrites your page class so that object pooling is no longer needed. It looks like upgrading to 5.2.5 should give you a better debugging experience. Josh On Mon, Apr 11, 2011 at 2:22 PM, Jim O'Callaghan <jc1000...@yahoo.co.uk> wrote: > Can anyone in the know advise on the JREs that best suit Tap 5.2.4 for > debugging? I’m using jdk1.6.0_21_x64 and finding a lot of things I try to > put watches on or inspect using Eclipse (3.4.1) resolve to null, and I have > to log them to get the true value – thanks. > > Regards, > Jim. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
