Rob Dennett <rob_dennett <at> tmit1.org> writes: > Yes, but would it be fair to say that it is a T4 best practice to create a > session-scoped ASO that handles all > non-Tapestry-specific page logic for each page (and maybe for each custom > component) in the application? Or should this logic live in the page class, > or in a HiveMind service or in a Spring bean?
It should be in POJO classes (Hivemind services and Spring beans are also POJO). Use session-scoped ASO's for data (state) that is pertaining to a particular usage session. As you have my book, you should check the chapter on database in particular the section "dividing the app into layers". -- Author of a book for learning Tapestry (http://www.agileskills2.org/EWDT) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
