+1 for changing this... it should be @StateObject or @UserStateObject or 
something else (Application implies an application wide scope rather than user 
session scoped) a real gotcha for newbies!
 
----- Original Message -----
From: "Geoff Callender" <[EMAIL PROTECTED]>
To: "Tapestry users" <users@tapestry.apache.org>
Sent: Wednesday, 5 November, 2008 3:30:18 PM GMT +02:00 Athens, Beirut, 
Bucharest, Istanbul
Subject: T5: @ApplicationState is misleading - voters wanted!

With the final version Tap 5.0 fast approaching, this may be the last  
chance to address issues of confusing terminology.

If you feel that the term @ApplicationState is misleading - that is,  
if you have ever felt that @ApplicationState implies a field will  
become shared between all users in all sessions - then please vote here:

        https://issues.apache.org/jira/browse/TAP5-274

G.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to