[ 
https://issues.apache.org/jira/browse/OFBIZ-4098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12979117#action_12979117
 ] 

David E. Jones commented on OFBIZ-4098:
---------------------------------------

This is an interesting request. For Moqui (www.moqui.org) I decided to go with 
ehcache itself for the cache implementation. The cache interface design I 
started with was based on the OFBiz cache API, and most of it worked pretty 
well but there were a few mismatches, and quite a few things I got rid of in 
the cache design because ehcache just doesn't support them.

Anyway, the implementation ends up being quite simple, the cache wrapper and 
factory in Moqui are complete and available here:

http://moqui.svn.sourceforge.net/viewvc/moqui/trunk/moqui/framework/impl/src/org/moqui/impl/context/CacheImpl.groovy?view=markup

http://moqui.svn.sourceforge.net/viewvc/moqui/trunk/moqui/framework/impl/src/org/moqui/impl/context/CacheFacadeImpl.groovy?view=markup

Chances are it would only take a few hours to implement this in OFBiz (plus 
time for whatever configuration mechanism you decide on, which is messy), but 
you would have to leave out (effectively disable) certain features that the 
OFBiz UtilCache supports. For example, I never could figure out how to get soft 
references working in ehcache.

> Ability to plug a new Cache Implementation
> ------------------------------------------
>
>                 Key: OFBIZ-4098
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-4098
>             Project: OFBiz
>          Issue Type: New Feature
>          Components: framework
>    Affects Versions: SVN trunk
>            Reporter: Philippe Mouawad
>   Original Estimate: 96h
>  Remaining Estimate: 96h
>
> Hello,
> I would like to contribute a patch to enable switching from Ofbiz native 
> Cache (today UtilCache) to another implementation like EhCache for example.
> To avoid big code impacts, UtilCache would stay the same and delegate to the 
> real
> cache implementation this will impact less classes and big impacts
> would stay in UtilCache package.
> Ability to plug another implementation like EhCache for example would enable 
> easily plugin with Terracota for example which on big Web Site gives much 
> performance enhancements.
> Is the format to contribute this kind of evolution also a patch ?
> Thank you
> Regards
> Philippe
> http://www.ubik-ingenierie.com

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to