On Fri, 09 Nov 2012 13:55:48 -0200, nhhockeyplayer nashua
<nhhockeypla...@hotmail.com> wrote:
Ok so I set my flag in the eclipse preferences VM section
-Dtapestry.production-mode=false
and I get dev mode as expected
______ __ ____
/_ __/__ ____ ___ ___ / /_______ __ / __/
/ / / _ `/ _ \/ -_|_-</ __/ __/ // / /__ \
/_/ \_,_/ .__/\__/___/\__/_/ \_, / /____/
/_/ /___/ 5.3.1 (development mode)
2012-11-09 10:42:56.540:INFO::Started SelectChannelConnector@0.0.0.0:8080
And when I breakpoint on one of my eventlink handlers... my homePage
variable is actually allocated properly... it is no longer null.
I am still trying to conceptually bang what you said into my head... and
still trying to understasnd what tapestry is doing or trying to do at
this level during the debugger... or how it is making my life easier.
Easy: page, component and mixin classes are transformed by Tapestry. Reads
and writes to fields of these classes are replaced by method calls. When
in development mode, the field remains and is updated by Tapestry. When in
production mode, which isn't supposed to be used when debugging, these
fields are not updated by Tapestry, as this would be completely useless.
I understand in PROD mode it is trying to streamline things ?... an
doesn't expect you to be in the debugger?
Absolutely no. That's why it's called 'production'. ;) Debugging is
supposed to be done in the 'development' mode.
And there is some kind of threadlocal storage being exercised? And a
swapping in of state ?
Yes for threadlocal, I don't know what do you mean by swapping of state.
Since Tapestry 5.2, which doesn't have a page pool anymore, the access to
fields are replaced by a Map in a ThreadLocal, as just one instance is
created for each page. In development mode, the fields themselves are
written, in production no, as concurrent request to the same page would
interfere with each other).
--
Thiago H. de Paula Figueiredo
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
