There are still dozens of Tapestry services that will need to be
changed/rewritten, though. I'm not against this, just saying it's a huge
change at this point - the way I see it, anyway.
-Filip
On 2008-09-17 18:12, Hilco Wijbenga wrote:
On Wed, Sep 17, 2008 at 09:03, Filip S. Adamsen <[EMAIL PROTECTED]> wrote:
@Scope does, indeed, make more sense than @Persist and
@ApplicationStateObject. I wouldn't mind that change, but is it feasible at
this point in Tapestry 5's development cycle?
Sure, just deprecate @Persist and @ApplicationStateObject and
introduce @Scope as their replacement. All old code will still work
and new code can use @Scope. (It's even relatively easy to automate
[i.e. script] the move from the old code to the new.)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
