Thanks for your help.. I went at looked a Scarab OM object
(AttributeManager) and copied the constructor. That made all the
difference.. I will submit a patch to the Torque docs about the change
needed to the constructor.
Now however, the caching is working great, but I am getting out of memory
errors on pages that never before had these problems. Even though I only
turned on caching for one specific class, that only should ever have maybe
80 objects in memory, a very small number!
I recompiled my OM objects with b5 but without Managers, and everything
works fine.. I no longer have the out of memory errors. Is it possible to
set something in my project-schema where only one table will use managers?
I think the overhead of JCS and Managers for all the objects not using them
is what is causing my issues....?
Eric Pugh
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
