Hi Lasitha, good practice to follow, thanks. can you explain more about about this null check, any example why we have to check? thanks.
lasitha wrote: > > On Nov 22, 2007 6:27 PM, Yunhua Sang <[EMAIL PROTECTED]> wrote: >> > Since the above events fire on both the original request and the one > from the redirect, you'll probably need a null check to differentiate: > load from db if null, attach to current session if not. > Lastly, i must admit that i usually just reload the object from the db > instead of @Persist-ing it. It's just less hassle and has rarely been > too slow. > > Oh, and if you do stay with @Persist, consider using flash persistence > instead of the default. > > Cheers, lasitha. > > > > -- View this message in context: http://www.nabble.com/T5%3A-Tapestry-Hibernate%2C-do-we-have-to-save%28%29--tf4718363.html#a13904685 Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
