[jira] [Resolved] (OFBIZ-7760) Removed from UtilCache the ability to persist entries in the file system

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Resolved] (OFBIZ-7760) Removed from UtilCache the ability to persist entries in the file system

Nicolas Malin (Jira)

     [ https://issues.apache.org/jira/browse/OFBIZ-7760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jacopo Cappellato resolved OFBIZ-7760.
--------------------------------------
       Resolution: Fixed
    Fix Version/s: Upcoming Branch

Patch committed in rev. 1751817

Added an entry to the Attic page:

https://cwiki.apache.org/confluence/display/OFBADMIN/OFBiz+Attic#OFBizAttic-Abilitytopersistcacheentriesinthefilesystem

> Removed from UtilCache the ability to persist entries in the file system
> ------------------------------------------------------------------------
>
>                 Key: OFBIZ-7760
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-7760
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: framework
>    Affects Versions: Trunk
>            Reporter: Jacopo Cappellato
>            Assignee: Jacopo Cappellato
>             Fix For: Upcoming Branch
>
>         Attachments: OFBIZ-7760.patch
>
>
> Removed from UtilCache the ability to persist entries in the file system.
> This feature has been contributed a long time ago as an experimental feature but never really matured into a production ready artifact: since it was contributed, no users asked about how to use it, or tested it, or reported bugs or enhancement requests.
> More importantly, the feature has always been disabled in the OFBiz framework (i.e. the widget code and the entity engine code were not using it).
> This removal should not impact our user base; however, after the removal, an entry to the Attic will be created to keep track of it and to make it easier, to interested users, to get this code, improve it (e.g. by making it dependent on a live external jar, for example MapDB instead of JDBM) and possibly contribute it back to the project.
> The most compelling reason for its removal is that the feature was based on a snapshot, unreleased version of JDBM, which is now a mostly dead project: for licensing reasons we are no more allowed to bundle jars in our releases. Additionally, having code that relies an old jar from a no more active project represents a maintenance issue for the community.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)