Priority: 2 Major
Resolution: Won't Fix
Affects Version/s: 2.0.1
Fix Version/s: None
Not sure whether that serves a purpose or not... Seems to be like that since 2006.
It was posted on the forum and I had a quick mail exchange with Greg on the subject:
Maybe you can have a look at this:
I'm not sure why BlockingCache.put is implemented as such... Certainly would be interested in some background though. Or is this something we might change?
Really no good reason. If I ever had a reason it would be on the javadoc. The thing to bear in mind is that you need to support backward compatibility with the web cache and anybody using the BlockingCache now. If you can do that I am happy with the change.