It has to be said that this API isn't always the most usable. I remember the get() method throwing exceptions in case the item was not found which was really cumbersom. Dunno if it changed since the last time I checked it out
On Thu, Nov 3, 2011 at 9:03 PM, Igor Babalich (Commented) (JIRA) < [email protected]> wrote: > > [ > https://issues.apache.org/jira/browse/DIRECTMEMORY-15?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13143488#comment-13143488] > > Igor Babalich commented on DIRECTMEMORY-15: > ------------------------------------------- > > Following to jsr107 could help in the class hierarchy organization and > classes naming by reducing time for class names and expected method > inventions . > > It is especially make sense for following to jsr107, as the work for that > specification is in active state and it is going to be part of Java EE7 > http://www.infoq.com/news/2011/08/jcache-jsr-lives > > The active development code for jsr07 could be found here: > https://github.com/jsr107 > > > > > Implement "JSR 107: JCACHE - Java Temporary Caching API" interface > > ------------------------------------------------------------------ > > > > Key: DIRECTMEMORY-15 > > URL: > https://issues.apache.org/jira/browse/DIRECTMEMORY-15 > > Project: Apache DirectMemory > > Issue Type: Improvement > > Reporter: Raffaele P. Guidi > > Priority: Trivial > > > > Implement "JSR 107: JCACHE - Java Temporary Caching API" interface (Not > that a lot of people really cares about this, but...) > > Useful link: > http://grepcode.com/snapshot/repo1.maven.org/maven2/net.sf.jsr107cache/jsr107cache/1.1/ > > -- > This message is automatically generated by JIRA. > If you think it was sent incorrectly, please contact your JIRA > administrators: > https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa > For more information on JIRA, see: http://www.atlassian.com/software/jira > > >
