Eric, you could
a) use the cache type 'count-limited' with a capacity that suites you needs, to avoid unlimited growth of the cache; please note, though, that doing so might not prevent you from running into the same cache eviction problem, especially then the capacity has not been selected carefully. b) use cache type 'time-limited' with a timeout that suites your needs, and (much in the same was as with option a) ) avoid unlimited growth of the cache; the note from option a) applies equally. and c) wait a couple of days until I commit a patch for issue 1102, which adds support for distributed caches to Castor JDO. One of the cache engines we'll be supporting is JCS, which can be used as a local cache only, too. When doing so, JCS (as well as e.g. OsCache) allows you to configure a disk overflow mode where anything above a defined threshold is written to a cache partition stored on a hard disk. Regards Werner Eric Anderson wrote: > > Maybe I am thinking about this the wrong way but I seem to be having > problems implementing castor with struts.. > > I am tring to do it so that struts and castor can share forms > (ActionForms) but running into some problems. > > It works great to use castor to populate the form. But by the time I > push that form object to the veiw, back to the controller, then try to > make an update, the cache has expired. (unlimited takes way too much > memory). > > Does anyone have a good example of how to implement castor with struts > and not have persitance problems? > > Thanks > > > > ------------------------------------------------- > If you wish to unsubscribe from this list, please > send an empty message to the following address: > > [EMAIL PROTECTED] > ------------------------------------------------- > > ------------------------------------------------- If you wish to unsubscribe from this list, please send an empty message to the following address: [EMAIL PROTECTED] -------------------------------------------------
