A collection class would not be ideal, using individual ASOs, each with a
specific unique type is the way to go.
On 10/2/07, Robert A. Decker <[EMAIL PROTECTED]> wrote:
>
> In the docs they use the example:
> public class MyPage
> {
> @ApplicationState
> private MyState _myState;
>
> . . .
> }
> and:
> "Any other component or page that declares a field of the same type,
> regardless of name, and marks it with the ApplicationState annotation
> will share the same value. It's that simple."
>
> Do people generally use a collection class for MyState and when
> needed, pull out the collection and then their variable? Or do you
> have multiple ApplicationState variables in your session and pull
> them out by name?
>
> How do you keep track of everything you have in your session? Maybe a
> custom Session class? Something like:
>
> public class MyPage
> {
> @ApplicationState
> private Session _mySession
> ...
> }
>
> public class Session
> {
> DataContext sessionDataContext;
> User loggedInUser;
> ...
> }
>
> Thanks,
> R
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Howard M. Lewis Ship
Partner and Senior Architect at Feature50
Creator Apache Tapestry and Apache HiveMind
