XPages Notes Client caching

I’m developing my first XPages app for the Notes Client after developing browser based XPages for the past year, and am experiencing terrible caching problems of the design elements. What am I doing wrong?

I make a change to the XPage, open it in the Notes Client and it’s the old version of the XPage that executes. If I close down the client and then Preview in Notes Client the XPage, then it does show the new version. If I then close the XPage in the client, ie closing the database, and then open the database again I see the previous version again! It’s driving me crazy!

Subject: Same problem

This happens to me too. Instead of shutting down notes if I change the name of the xpage, it does not cache it. But you have to do that each time you preview in Notes.

Subject: Has this been solved?

I have run into this as well on a Notes 9 client. Have to shut down the notes client in order for it to see any design changes.

Subject: Haven’t seen it on 9 yet.

I haven’t seen this issue on Notes 9 yet. But previous versions, one of the most common causes of this was due to broken XSP code, preventing rebuilding of the XPage.

To check this, you can try launching with the OSGi console active.

You do this through the following:

Target: C:\Lotus\Notes\notes.exe -RPARAMS -console -debug -separateSysLogFiles -consoleLog

Start In : C:\Lotus\Notes\framework\

After that check the OSGi console for any errors when trying to load the page.

Also if you hit the refresh smarticon does the issue still persist?