Hey
(Yes, I'm on holiday for a bit less than two more weeks, but I'll try to
keep up with the lists)
Peter Braswell wrote:
> I suspect its to monkey around with the jboss xml file
> to specify minimum and maximum instances and in the
> client create a number of connections greater than the
> minimum specified in the xml. Am I on the right
> track?
>
> Essentially I want a scheme to force activation and
> passivation.... :-)
I will be writing a new entity cache when I get back. I have it all
figure out in my head, no problemo. It will support LRU, FIFO, NRU,
Random, and "No Passivation", all in one cache. The cache sizing will be
static only at first (i.e. you set a limit and that's it), but I intend
to implement dynamic Working Set algos since that would be more
efficient.
In addition, the cache will adhere to the plugin start/stop commands, so
when stop()ped it will passivate all instances. I.e. in your tests you
would call some entity to get it activated, then stop() the container
(which in turn will stop the cache -> passivate). After that you start
the container and retrieve the call log.
Good enough?
/Rickard
--
Rickard �berg
@home: +46 13 177937
Email: [EMAIL PROTECTED]
http://www.telkel.com
http://www.jboss.org
http://www.dreambean.com
