RE: Remote debugging a Tapestry application

That's incorrect. Tapestry pages / components are byte code transformed such that properties are stored in PerThreadValue instances. In development mode tapestry duplicates the values into the bean properties to make debugging easier. On 5 Apr 2017 09:30, "Ankit Jain"

RE: Remote debugging a Tapestry application

The problem you are talking about is independent of development/production/remotedebugging. You can use sysout or logger to trace the values as watch will not be able to show you the real value of global objects in the page. Note: I am assuming that you are trying to see the value of the global