portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Sean Taylor <da...@bluesunrise.com>
Subject Re: JS 2.1 - render phase not called when actionResponse.sendRedirect used
Date Tue, 20 Mar 2007 18:34:43 GMT

On Mar 20, 2007, at 11:12 AM, Aaron Evans wrote:

> On 3/20/07, David Sean Taylor <david@bluesunrise.com> wrote:
>>
>> I believe the portal is behaving correctly in this case as its
>> invalidating the current page only
>> The spec doesn't really address multiple page cases, leaving it open
>> to interpretation
>>
>> The way its behaving right now, only portlet windows on the same page
>> are invalidated on an action, so windows on a different page are not
>> invalidated
>>
>
> I think this sounds reasonable.
>
>> I think there are a couple of ways we could handle this :
>>
>> * don't use portlet caching on your particular portlet (just remove
>> the <expiration-cache> tag
>
> This solution works fine for me. It is not the type of portlet that
> would be cached much anyway.  In fact, I had the expiration-cache set
> to -1 which I thought meant never cache but I guess that means never
> expires?
>
> In any event, I removed the tag and it is working as advertised.
>
-1 == cache forever (or at least up to the portal)
  0 == cache turned off which is the same as absense of the tag



---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org


Mime
View raw message