Well another weekend spent on ehcache.
Added a long requested feature to accept keys and values that do not implement Serializable. This makes ehcache suitable for a lot more purposes. I was always afraid of the subtleties involved with NonSerializable Elements getting into the system and then not being able to be persisted to DiskStores or replicated. But it is just a matter of gracefully degrading and logging warnings. It was quite simple really.
Also fixed some minor bugs to do with rare edge conditions. This makes ehcache more robust.
There is only one old bug to fix. No patches to process. And pretty much all the feature requests that are going to get into this release are in.
So what is stopping me from releasing 1.2? I am getting desperate for reasons not to release it. The problem with open source projects are either no one uses them and you can change them as often as you like, or they are widely used like ehcache and you become ultra cautious.
I probably want to do the following before I release:
– fix that last bug
– I promised the Hibernate guys a new ehcache plugin.
– more torture tests for replication.
Perhaps next weekend…
Thanks for the hard work. It shows in the product.
Thanks for the hard work man.
Not sure if U look thru the bug list on Sourceforge,
but there’s one major bug which is blocking me
badly now.
U removed methods that get/put(Serializable) or
Element(Serializable, Serializable).
What happens then, is that code that was compiled with the old version of ehcache 1.1 will now throw
NoSuchMethodError when calling any of these. These
2 especially are called by all code which depended
on Ehcache (e.g. JCaptcha, and Hibernate 3.0/1)
I’m writing a forum now, and it’s bombing because
of this.
— Ugorji
Ugorji,
Yes I saw your report on Sourceforge. I have added Serializable methods and constructors which fix your reported problems. See the full comment on Sourceforge.
Greg