Hello Daniel, Firstly, never store a component in a session scoped bean, it's bad, like crossing the streams in Ghostbusters. What you need to store in session scope is the DataModel. If you need it to do some funny stuff like lazy fetching, or something else, you can make your own implementation to deal with data the way you want (maybe cache a good chunk in as a singleton if the issue show up when there's many users online?). Another option would be to use the pageFlowScope which is more durable than request and less than session.
Regards, ~ Simon On 7/30/07, Hannum, Daniel <[EMAIL PROTECTED]> wrote: > > I have a few big Trinidad tables (UIXTable) that are stored in session > scoped backing beans. Unfortunately, they are causing memory problems, so > I'm trying to free the memory when you navigate away from the few pages > where they are used. I also know that request scope is too short-lived for > them. > > > > First I cleared out the data lists backing the tables by setting the > references to null. However, they aren't garbage collected because the > SortableModel and the table components themselves still contain references > to the lists. I have tried setting setValue(null) on the tables and even > nulling out the components themselves, but there is always another > reference. > > > > Since this is looking like a big hack at this point, here's my question. > Is there a way to programmatically tell a UIXTable (CoreTable) to delete the > data it's holding onto? I want to reset it to an empty state. This seems to > happen automatically if I change the backing list to an empty list and > redisplay the page, but I need it to happen without a page redisplay (i.e. > completely programmatically because this logic will be in a method called at > the top of other pages). > > > > I hope that made sense. I haven't seen this asked before, and I hope > there's a clean way to do this. > > Dan > > ------------------------------ > > * ***Note:The information contained in this message may be privileged and > confidential and protected from disclosure. If the reader of this message is > not the intended recipient, or an employee or agent responsible for > delivering this message to the intended recipient, you are hereby notified > that any dissemination, distribution or copying of this communication is > strictly prohibited. If you have received this communication in error, > please notify the Sender immediately by replying to the message and deleting > it from your computer. Thank you. Premier Inc. * >
