[ http://jira.magnolia.info/browse/MAGNOLIA-1495?page=all ]
Grégory Joseph resolved MAGNOLIA-1495.
--------------------------------------
Resolution: Fixed
done.
Just for the record, the piece of code that was supposedly going to generate
the cache:
private void cachePage(Content page, HttpServletRequest request) {
// Collection children = page.getChildren();
// Iterator iter = children.iterator();
// while (iter.hasNext()) {
// Content item = (Content) iter.next();
// MockCacheRequest mock = new MockCacheRequest(request, item);
// // @todo fix the canCompress parameter
// this.cacheManager.cacheRequest(mock, true);
// if (log.isDebugEnabled()) {
// log.debug("Trying to cache request:" + mock.getRequestURL());
// }
// cachePage(item, request);
// }
}
> CacheManagementPage does nothing : drop it
> ------------------------------------------
>
> Key: MAGNOLIA-1495
> URL: http://jira.magnolia.info/browse/MAGNOLIA-1495
> Project: Magnolia
> Issue Type: Task
> Components: admininterface
> Reporter: Grégory Joseph
> Assigned To: Grégory Joseph
> Fix For: 3.1
>
>
> The CacheManagementPage was supposed to force the generation of the complete
> cache. The code is however completely commented out, so it just does nothing.
> I'd be in favor of dropping this.
> However, that feature could be useful along with other tools like
> cache-flushing, workspace-synchronization etc.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia.info/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/developer.html
----------------------------------------------------------------
