Achim Staebler commented on Jun 29, 2011

Re: Caching with the Web Content Viewer (JSR 286) Portlet

David, you are correct, we've tested this on Portal 6.1.5 and 7.0, both running on WAS 7.0.

I'm going to update the article with a separate cachespec.xml that also works on 6.1.5 with WAS 6.1.

Gianluca Bruno commented on Jun 28, 2011

Re: Caching with the Web Content Viewer (JSR 286) Portlet

Has anyone successfully applied the cachespec to a Portalv7 and WAS7 environment? I was unsuccessful in my attempts with the above cachespec.xml.

yang us_ibm_com commented on Jun 24, 2011

Re: Caching with the Web Content Viewer (JSR 286) Portlet

UGH, formatting is messed up, trying again...)

For Portal/WAS 6.1, try removing these XML lines from the sample cachespec.xml:

.component id="javax.portlet.render_part" type="attribute".

.value.RENDER_MARKUP..value.

..component.

yang us_ibm_com commented on Jun 24, 2011

Re: Caching with the Web Content Viewer (JSR 286) Portlet

(UGH, formatting is messed up, trying again...)

For Portal/WAS 6.1, try removing these lines from the sample cachespec.xml:

/

/RENDER_MARKUP/

/

yang us_ibm_com commented on Jun 24, 2011

Re: Caching with the Web Content Viewer (JSR 286) Portlet

(UGH, formatting is messed up, trying again...)

For Portal/WAS 6.1, try removing these lines from the sample cachespec.xml:

RENDER_MARKUP

yang us_ibm_com commented on Jun 24, 2011

Re: Caching with the Web Content Viewer (JSR 286) Portlet

For Portal/WAS 6.1, try removing these lines from the sample cachespec.xml:

RENDER_MARKUP

yang us_ibm_com commented on Jun 24, 2011

Re: Caching with the Web Content Viewer (JSR 286) Portlet

I believe this article was tested on WP 6.1.5.x on WAS 7.0.

Robert Greenwood commented on Jun 2, 2011

Re: Caching with the Web Content Viewer (JSR 286) Portlet

My attempts at this so far have failed. Is this feature supported for WAS 6.1/Portal 6.1.5? What are the version requirements for this functionality?