Seems like a good idea to me. Do we have an agreed on definition of
what 'beta' means? We decided this was version 4 because it was a big
change, and keeping backwards compatability was not always going to be
possible. I see no need to cling to this confusing/frustrating part of
Tapestry in the name of 'beta'. 'beta' to me is not an API freeze
gaurantee. 'rc' would be to me, but not 'beta'.
However, Geoff's warning of Spindle not supporting this might be more of
a concern. Geoff - what would that actually mean to Spindle? eg. would
it not work at all? Some features would no longer work?
Richard
Howard Lewis Ship wrote:
The method initialize() is invoked from AbstractPage's default (no
arguments) constructor.
This is truly problematic. It dates back to an earlier time in
Tapestry's life, before runtime code generation took care of
initializing and re-initializing properties.
It causes a major headache for me ... it means that you can't easily
mock a page the way you can mock an component (using EasyMock and the
EasyMock class extension). EasyMock trips over the initialize() call
from the default constructor. This actually happened to me when I was
trying to demonstrate EasyMock and testing for Tapestry at a client.
I would like to eliminate this method now, rather than wait for 4.1 (I
marked it as deprecated sometime during 4.0). Doing so will allow us
to document the proper Tapestry testing story for pages, not just
components.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
