Command link navigation problems in IE but not firefox

Hi,

I've developed an application using JSF and SDO. I have several pages where the user is displayed data from the database and pages where the user can add data , edit data and delete data.

Each page has a jsp fragment contained in the page. This is based on faces and is the naviation menu. Each link in the menu is a command link and has navigation rules which are global. Now the problem I get is that when I sometimes nvaigate between pages using the navigation or command links in a page the page just refreshes and displays the same page again. But if I keep trying to click the link again then after a few attempts the link goes to the page i've requested. I've added system outs on the actions for the links to see if they are getting called when the page just refreshes. The answer is no as the system out line is never printed unless the action of the link is actually executed.

Now the problem is that this only occurs in ie and NOT in firefox. I'm really confused now!!

Here is some techinical details to help narrow down my situation:

I'm using wsad 5.1.2 which has faces 1.0, ie 6, firefox 1.0.3.

Any help would be appreciated!!

[1192 byte] By [notagaina] at [2007-10-3 3:29:15]
# 1
Disable browser cache in IE and see if it solves the problem.Is the webapp session or request scoped?
BalusCa at 2007-7-14 21:23:01 > top of Java-index,Enterprise & Remote Computing,Web Tier APIs...
# 2
Hi,The browser cache is disabled. The app is session scoped.
notagaina at 2007-7-14 21:23:01 > top of Java-index,Enterprise & Remote Computing,Web Tier APIs...
# 3

doh! i've solved this problem now....well for now its working perfectly but i'll have to do a bit more testing.

For anyone that has this problem here was my solution...

- In IE i went to tools > general tab > settings

from this menu choose check for newer versions of stored pages to automatically. I previously had every visit to the page.

This seems to have fixed my problem and the reason why it worked in firefox was because the settings for caching were different.

notagaina at 2007-7-14 21:23:01 > top of Java-index,Enterprise & Remote Computing,Web Tier APIs...