I didn't want to try and have a conversation about dirty checking within JIRA...
What are your thoughts on dirty checking? Seam could keep track of field/method access and then simply not call the DataBinder methods if there haven't been any changes since the previous wrap/unwrap invocations. Within wrap/unwrap the DataBinder could be forced to do it's own dirty checking based on information stored in a custom wrapped object (approach currently taken). Seam could signal the DataBinder that it has observed access to the object and that it might be dirty (via additional param on wrap/unwrap?). Then the binder could take its own action as it wishes. wrap/unwrap would be called on each request. -Jim View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3946615#3946615 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3946615 ------------------------------------------------------- All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642 _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
