Hi,
I have tried this solution and it is not working in my case.
Is it sure that this works??
Carlos.
sbelt wrote:
> Which portlet class are you using? One from the distribution or a portlet
> class of your own? I am using Jetspeed on an Intranet; one of the portlets
> on the users home page is a summary of their daily schedule - this requires
> an update every time the page is refreshed, ie, it cannot be cached. I'll
> share with you our solution (though be warned that the PortletAPI
> discussions may - or may not - alter this in the future)
>
> Assuming you are using an existing portlet class, here is what I would
> suggest. (I'll use RSSPortlet as an example):
>
> - copy \src\java\org\apache\jetspeed\portal\portlets\RSSPortlet.java to
> ...\RSSCurrentPortlet.java
> - Modify the RSSCurrentPortlet.java. Add the following method to the class.
> /* tells jetspeed not to cache this content*/
> public boolean isCacheable ( )
> {
> return false;
> }
> - modify the jetspeedconfig.jcfg to use RSSCurrentPortlet instead of
> RSSPortlet
> - Run the build scripts to create your jar/war file(s).
>
> Now you won't have to sacrifice the performance of the entire system to
> support this single portlet! I had actually modified many of the portlets so
> I can pass a parameter indicating whether the portlet should be cached.
> (Basically, read the parameter in the init() method, then return that value
> in the isCacheable() method rather than always returning false)
>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/jetspeed@list.working-dogs.com/>
List Help?: [EMAIL PROTECTED]
