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 mechanism similar to what you > have. It was always a lot of unwanted configuration. This > streamlined approach means no configuration: just slap > @ApplicationState on a field and you are done. > I guess I can always define a wrapper object with a unique type. Thanks for the feedback, Karl -- View this message in context: http://www.nabble.com/%40ApplicationState-fields-keyed-by-class%2C-not-instance-tp14924062p14951480.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
