I believe you will be able to see the values if you are in development mode.

On Tuesday, April 4, 2017, g kuczera <gkucz...@gmail.com> wrote:

> Hi everybody,
> I wanted to speed up my work and try out the remote debugging from Eclipse.
> It indeed works (I use jetty:run on localhost and then remote debugging
> configuration from Eclipse), the breakpoints are hit. The big problem is
> the wrong values of the pages' fields - all of them equal null or other
> default value (eg. the boolean fields equal false). After passing the field
> to the method, it's value is read correctly.
>
> I use Tapestry 5.3.7 and Eclipse Neon. The application is run in the
> production mode and I have not yet tried the development mode (I have some
> configuration problems, probably not connected with Tapestry). Is there any
> difference in this case between these two modes?
>
> The project is managed by maven. The maven-compiler-plugin plugin is in
> version 3.1 and is configured with settings:
>           <debug>true</debug>
>           <debuglevel>lines,vars,source</debuglevel>
>
> I think that my problem is connected with this three ead:
> http://apache-tapestry-mailing-list-archives.1045711.
> n5.nabble.com/Debugging-variables-td4296888.html
>

Reply via email to