Howard Lewis Ship wrote:
>
> Long experience has shown that these objects tend to be singletons.
> It's generally things like the user's identity or account information
> or shopping basket.
>
Yes, that is mostly true.
Howard Lewis Ship wrote:
>
> Earlier versions of Tapestry uses a mechani
I am new to Tapestry 5 (never looked at previous versions).
Forgive my possibly naive question:
It seems ApplicationState annotated fields are keyed by class, so this
really supports
only one instance (singleton) per class (and per scope, usually session).
Would it not be useful to be able to pa
