IView not processed for second time, but 'old' cached data is displayed...

Question

<b>I have the following scenario</b>:
In IView 1, I select a notification number. Then, I click on a button to create a service order.
This calls IView 2, and the notification number is passed as a request parameter to IView 2.
The problem happens when I close the popup and select another Notification to do the same thing with. When the popup is called, the old data is still there. The IView itself is not processed (no doInitialization etc).
<b>Details</b>:
The parameter is passed correcty to the other IView.
This is done by using:
a = window.open('<%=String.valueOf(Constants.QUICKSERVICEORDER_COMPONENT)%>?notificationnumber=<%=R3_Notification.getNotificationNumber()%',
'createserviceorder',
'toolbar=no,menubar=no,location=no,personalbar=no,titlebar=yes,scrollbars=auto,resizable=yes,width=600,height=500');
In the second IView's java part, the parameter is picked up:
notificationnumber = request.getParameter("notificationnumber");
That did work in the previous Portal version, so there's really no reason to believe it's wrong now...
But after upgrading to EP6, it does not behave the same way anymore.
I added messages to the defaultLogger, to write to the log at doInitialization.
Then, I can see that output is NOT written...
It looks like the popup IView is not being called again, but just displays the OLD data.
Unless I upload the component again to the Portal.
Then it works. Once. Looks like a caching issue to me.
Just clicking on the 'x' to close the window doesn't seem to clear the cache.
So I have to find a way to refresh this IView or clear its Cache or something...
But how is a mystery...
Anyone else encounter this problem?

Answer 1

Yes, that solved the problem.
Thanks very much!
Background info (might be helpful to others...)
We migrated from 5.0 to Portal 6.20. This caused problems with caching.
There are differences between caching in those versions. But the main reason was that the portal version information was set in the portalapp.xml file...
To solve the issue, the lines referring to the portal version have been removed from the portalapp.xml:
  <application-config>
    <property name="ClassLoadingPolicy" value="5.0"></property>
    <property name="DeploymentPolicy" value="5.0"></property>
    <property name="AuthenticationPolicy" value="5.0"></property>
  </application-config>
Also, a line was added in the Portalapp.xml:
    <property name="ALLOW_BROWSER" value="No"/>
If the component is called directly (as in our case), then the Iview caching will not be used. All the caching has to be done via the portalapp.xml file.