In Tapestry 4, they are more generic, called "ASOs". You can think of Visit as a legacy ASO, but it's better to create your own and name them differently (no Visit) since that conflicts with a deprectated method (Object getVisit()) on BasePage.
On 4/4/07, Gareth <[EMAIL PROTECTED]> wrote:
Are we supposed to use some other form of session persistence, or is it a good pattern to create a user Visit Object and keep all user session variables inside it? Thanks ___________________________________________________________ What kind of emailer are you? Find out today - get a free analysis of your email personality. Take the quiz at the Yahoo! Mail Championship. http://uk.rd.yahoo.com/evt=44106/*http://mail.yahoo.net/uk --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Howard M. Lewis Ship TWD Consulting, Inc. Independent J2EE / Open-Source Java Consultant Creator and PMC Chair, Apache Tapestry Creator, Apache HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
