> The thing that I do not understand is why the current
> VelocityPortlet defaults to returning isCacheable of "false".
> All that this means is that the portlet object is re-created
> upon each client request and not cached as an object. Is it
> safe to default this to "true" - or at least make it
> configurable from the portlet init parameters?
I think it would be better as true, esp. since so many portlets are
based on VelocityPortlet.
Not sure what the initial intent was there...
>
> I plan to cache the content as a member variable of the
> portlet - is this the right place - or should I be using the
> Cache Service - thus allowing the content to be cached even
> if the isCacheable flag is false?
>
Take a look at the WebPagePortlet, which caches its own content
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
