It's not an issue with FlexibleStringExpander - since the same instance
is being used for both lines (and the instance cache never expires).
I would recommend looking at the content widget - maybe something weird
is going on there.
-Adrian
Chris Howe wrote:
from today... 693619
----- Original Message ----
From: Adrian Crum <[EMAIL PROTECTED]>
To: [email protected]
Sent: Wednesday, September 10, 2008 11:41:06 AM
Subject: Re: Screen Widget Cache, Dataresource, FlexString Error
What revision are you using?
-Adrian
Chris Howe wrote:
I am getting an undesired result with the following:
<screen name="main-content">
<section>
<widgets>
<label>${parameters.dataresourceId}</label>
<content dataresource-id="${parameters.dataresourceId}"/>
</widgets>
</section>
</screen>
On each request with a different dataresourceId value, the <label> updates, but the
<content> does not until the widget.screen.locationResource.expireTime cache setting
elapses. This leads me to believe that the screen is getting cached after the
FlexibleStringExpander does its magic on the content element. I can't imagine this being
the expected result. Can anyone help me zero in on the fix while I dig? Thanks.
