Any ideas, anyone???
Would you be able to provide a war for us to test? You can send that to me in email: pjha AT redhat DOT com. Also which jboss portal version are you using?
Prabhat can you please give a short explanation, if expiration-cache should do what analyzediz described? Is it true that expiration-cache set to 0 should give a behaviour, where each call to that portlet will return a "fresh" new portlet instance?
Perhaps he (and i) misunderstood something? Another point, in exampled is see this setting will be set to -0. Is there a difference between 0 and -0 ??? I hope 0 = -0, but perhaps i am wrong ...
Thanks for answering,
- JBoss Portal 2.6.5 GA
- Richfaces 3.2.2 GA
- PortletBridge B4
- Part from http://www.scribd.com/doc/4857633/portlet1-0prdspec:
A portlet that has defined an expiration cache in its portlet definition mayprogrammatically alter the expiration time by setting the expiration-cache property in the RenderResponse object. If the expiration value is set to 0, caching is disabled for the 25portlet. If the expiration-cache property is set to -1, the cache does not expire. If during a render invocation the expiration-cache property is not set, the expirationtime defined in the deployment descriptor must be used. For a portlet that has not definedexpiration cache in the deployment descriptor, if the expiration-cache property is set itmust be ignored by the portlet-container.