Submitted by David De Vos on Jan 16, 2012 1:53:19 AM

Re: Web Content Management Caching and Pre-rendering

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

Submitted by Pete R Raleigh on Jan 16, 2012 12:05:14 AM

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"

Submitted by Michel Wigbers on Feb 28, 2011 8:07:07 AM

Re: Web Content Management Caching and pre-rendering

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

Submitted by Evan B Borysko on Jan 3, 2011 10:27:19 PM

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?

Submitted by Pete R Raleigh on Mar 22, 2010 6:03:41 PM

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?

Submitted by Matthias Falkenberg on Nov 18, 2008 7:15:32 AM

Extension to given cachespec.xml samples

Hi there,

The sample cachespec.xml files in the section "Rendering Portlet Examples" are nice. I would like to propose some extensions though.

On the one hand, when using cache specifications as currently shown, issues with multiple rendering portlets on a single portal page will arise since the cache ID only contains the WCM_GLOBAL_CONTEXT component.

An unique identifier for portlet instances should be incorporated into the cache ID, i.e., at least one component in the cache-id stanza of a cache entry should refer to the namespace of the portlet instance being rendered. Also a distinction between anonymous and authenticated users should be made. (see also { Link } by Filip Zawadiak)

Moreover, I would suggest to consider the WCM_CONTEXT parameter in the formation of the cache ID. It is set as query parameter to navigational URLs generated within the local rendering portlet if the portlet does not broadcast links to pages; in this case, there won't be a WCM_GLOBAL_CONTEXT parameter. To ensure that the content displayed by a portlet instance changes when clicking, say, links generated by a Navigator component, the WCM_CONTEXT must be considered in the formation of the cache ID.

The sample given below implements the proposals:

<?xml version="1.0" ?>

<!DOCTYPE cache SYSTEM "cachespec.dtd">

<cache>

<cache-entry>

<class>servlet</class>

<name>/jsp/html/view-original.jsp</name>

<property name="store-cookies">false</property>

<property name="consume-subfragments">true</property>

<cache-id>

<component id="UNIQUE_ID" type="attribute">

<required>true</required>

</component>

<component id="WCM_CONTEXT" type="parameter">

<required>false</required>

</component>

<component id="WCM_GLOBAL_CONTEXT" type="parameter">

<required>false</required>

</component>

<timeout>300</timeout>

</cache-id>

</cache-entry>

</cache>

As seen above, the cached JSP is called view-original.jsp. This JSP (the original of the rendering portlet) is included by a new view.jsp of the local rendering portlet whose task is to generate the UNIQUE_ID request attribute that is a mandatory part of the cache ID, e.g.:

<%@ page session="true" contentType="text/html" %>

<%@ taglib uri="/WEB-INF/tld/portlet.tld" prefix="portletAPI" %>

<portletAPI:init/>

<%

portletRequest.setAttribute("UNIQUE_ID", portletResponse.encodeNamespace(portletRequest.getUser()==null?"anonymous":""));

%>

<jsp:include page="view-original.jsp"/>

Submitted by David de Vos on Nov 6, 2008 1:31:25 AM

Re: Authoring Tools problem with Servlet Caching

You should open a PMR for this issue so see if anything can be done to fix the problem.

Submitted by John A James on Aug 26, 2008 12:22:35 AM

WCM Forum

Hi - these kinds of troubleshooting questions will probably get more responses at the WCM forum: { Link }

Submitted by Kritsana Piriyakitpaiboon on Aug 24, 2008 9:58:03 AM

Authoring Tools problem with Servlet Caching

H, I've used Servlet Caching with local rendering portlet of WCM. The content is rendered completely and also cached. However, there is a problem with content that has Authoring Tools. I cannot use any authoring tools (add/edit/delete) if the content was cached. Please help suggest as I need servlet caching for performance reason and also need authoring tools to work as it is a requirement of my customer.

Submitted by David de Vos on Jul 22, 2008 12:47:52 AM

Re: Regular expressions in Servlet-Caching

In response to the question about Regular expression support in servlet-caching, you would have to ask the Dynacache team.

Submitted by WartookMan on Jul 14, 2008 8:15:20 PM

Web Content Management Caching and pre-rendering

> Although servlet caching cannot cache personalized content...

 

We don't want to cache personalized content since we want the Portal PZN Rules to run based on the current session Cookie information, which may be updated even when viewing cached content. Our personalized areas will be served via iFrames - sourcing a single URL (one of many "personalized" content pages) containing a WCM Personalization Component. We will most likely store these content items in a separate Site(area) within the Library, so the URLs of Personalized content will be easily distinguished.

 

There doesn't seem to be an option for Regular Expressions, and having to explicitly exclude (using ) each individual personalized page seems very limiting.

 

Are Regular Expressions going to be supported in any future release?