0 Replies Latest reply on Apr 28, 2008 7:19 PM by Andy Conn

    Over reliance on SESSION scope for @DataModel in examples

    Andy Conn Newbie

      Most of the seam example applications (all cept wiki) combine @DataModel with ScopeType.SESSION. This seems contrary to the seam philosophy of minimizing session maintained data.  This would appear to be particularly problematic if large query results were being maintained.

      I am building a system that will have dozens upon dozens of different query - list - create/retrieve/update/delete applications. 

      What is the right approach query - list @DataModal with regard to memory management?