David De Vos commented on Jan 16, 2012

Re: Web Content Management Caching and Pre-rendering

Thx pete, just updated the document to fix both issues.

Pete R Raleigh commented on Jan 16, 2012

Re: Web Content Management Caching and Pre-rendering

A couple of typos:

* HEADING: "How to configure servlet-caching for servlet rendeing"

* Directly under this heading, point 3, "[WPS_ROOT]\wcm\installableApps" does not exist. It should be "[WPS_ROOT]\wcm\installableApps"

Michel Wigbers commented on Feb 28, 2011

Re: Web Content Management Caching and pre-rendering

please correct Omifind to Omnifind in your documentation. It´s also an IBM product

Evan B Borysko commented on Jan 3, 2011

Servlet Caching and Pager for Menu

It appears the settings listed above for Serlvet Rendering cache in Cachespec.xml don;t account for parameters added to links for paging through a result set; WCM_PI and WCM_Page.xxxxxxxxxxx. WCM_PI is not difficult to add, but the WCM_Page.xxxxx seems to be a dynamic parameter name. Has anyone figured out how to make this work so you can cache pages with Pagers?

Pete R Raleigh commented on Mar 22, 2010

Web Content Management Caching and pre-rendering

If I need to find all references to the current Content item, I'll need to use the API via a JSP component. Is it possible to retrieve the current Content item path using a JSP, via pre-rendering? Does the JSP have any awareness of the current HTTPRequest object?