Howard Lewis Ship <hlship <at> gmail.com> writes: > > 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. >
I'd vote +1 (non-binding). Reasoning: By now, Tapestry 4.0 is completely incompatible with the 2 production Tapestry 3-applications I have out there. A silent upgrade, or phasing-in of Tapestry 4's new features is not possible. Changing this now will save a lot of pain later and allow all new application development based on Tapestry 4 (I'm currently developing based on the beta releases) to go forward towards 4.1 without added refactoring cost, while Tapestry 3 applications need major refactoring anyway. best regards, Jonas Maurus --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
