Thank you for the tip. It was the conditions. I first tested for the existance of the urlParameter, whereas you test first for the existance of the scoped variable. That is the trick. It also works with a requestScope.

 

It has one deficiency though and that is that the browser URL stays the same http://myServer.eu/path/dbname.nsf/page.xsp?param1=999 regardless of the actual search, which is somewhat confusing. Is there some way to clear the parameter from URL?

- The only way I know to do this is to compute the new URL and reload the page completely using context.redirecToPage().  Then the address bar in the browser will reflect what's actually in force.  XPage actions on the same page, even full refreshes, tend not to update the URL for any reason, making it essentially impossible for a bookmarks to work correctly out of the box.

 

Hope this helps...

In the end I used context.redirectToPage(). This performs the search and leaves the URL clear of any parameters. The disadvantage is that the initial search is not bookmarkable. One could probably get around that by coding the redirect to occur on the next click of the search button rather than immediately. But in my particular case that would mean adding some transfer of many requestScope variables to sessionScope ones and the back on the load of the page, which I did not do. 

 

This is the code I used. 

if((context.getUrlParameter("par1")!="")) {

sessionScope.put("par1",parseFloat(context.getUrlParameter("par1")));

sessionScope.put("renderResults", true);

sessionScope.put("urlRedirect", true);

context.redirectToPage("XPage.xsp",true);

} else {

if(sessionScope.urlRedirect) {

requestScope.par1e=sessionScope.par1;

requestScope.renderResults=sessionScope.renderResults;

sessionScope.remove("par1");

sessionScope.remove("renderResults");

sessionScope.remove("urlRedirect");

}

}