EHCache 0.5 was released today. It has the backport to JDK1.3 and
JDK1.2 that has been discussed in this thread included.
The Changelog follows:
EHCache-0.5
===
Bug Fixes
-
- Implemented not creating a Disk Store when overflowToDisk="false" is
set in ehcache.xml
- toString() met
Great :)
Greg Luck wrote:
Gavin
Done.
I have changed logging to commons-logging and have added LRUHashMap
from commons-collections. This, along with some packaging changes will
be in CVS later today.
Greg Luck
On 15/11/2003, at 10:08 AM, Gavin King wrote:
We already have a dependency to
Gavin
Done.
I have changed logging to commons-logging and have added LRUHashMap
from commons-collections. This, along with some packaging changes will
be in CVS later today.
Greg Luck
On 15/11/2003, at 10:08 AM, Gavin King wrote:
We already have a dependency to commons-collections, so perh
Luck" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, November 15, 2003 1:10 AM
Subject: [Hibernate] EHCache and JDK1.4
> Hi
>
> EHCache does require the use of JDK1.4.
>
> Specifically we use:
>
> - LinkedHashMap, which provides us with an LRU Hash
We already have a dependency to commons-collections, so perhaps just use
commons SequencedHashMap instead of LinkedHashMap.
Greg Luck wrote:
Hi
EHCache does require the use of JDK1.4.
Specifically we use:
- LinkedHashMap, which provides us with an LRU HashMap
- JDK1.4 logging
- SoftRefererenc
On 15 Nov (09:10), Greg Luck wrote:
> I was pretty keen to use the java.util.LinkedHashMap, because the
> combination of a doubly-linked
> list combined with a Hashmap in JCS was the source of the memory leak
> in it. The memory store code
> went from around 1500 lines down to a few hundred and
Hi
EHCache does require the use of JDK1.4.
Specifically we use:
- LinkedHashMap, which provides us with an LRU HashMap
- JDK1.4 logging
- SoftRefererences
I guess there is a lot of production code out there on JDK1.3 and
earlier. I could replace
the JDK1.4 logging with commons logging and the j