I am developing an application on xpages and I have the following problem:
I use dynamic view panel with customizer bean. The customizer bean is based on the Jesse Gallagher bean available on GitHub (https://github.com/jesse-gallagher/Domino-One-Offs/blob/master/mcl/reports/DynamicViewCustomizer.java).
The problem is that after a few minutes of inactivity in the application, the navigation components (Pager Expand / Collapse, Pager, and PagerSizes) stop responding. The document access link works normally. If a refresh is run in the browser, the navigation components will work again.
If I remove the bean customizer the problem does not happen.
Does anyone know what the cause of the problem is and how to solve it?
Thaks a lot!
Marcus
Put Keep Session Alive controll from Extension Library to your page and set the delay for example to 60s. If this helps, you can change this to higher value.
The real cause of the problem was that I was adjusting some component and testing at the same time, without giving a reload in the application in the browser. This causes the behavior of the application to be abnormal. That way if you are testing and concurrently changing something in some component of the application, reload the application in the browser.
Related
So I have a Shell that has a home page and a settings page.
The settings page makes changes to a singleton service that the home's ViewModel is binded to (MVVM).
I have set up break points on the PropertyChangedEvents of elements on the Home page and they hit as soon as changes are made to the service's properties and their PropertyChanged is executed.
However, upon going back to the home page via the Shell, the page's UI only updates when the page is active and visible. This causes fields to flash when they change. But the breakpoints suggest that they should have updated before.
Is there a way to force refresh the UI before or are there any other alternatives?
For now I have made my view perform a Fade In animation so that changes to the ViewModel don't cause flashing.
Even I have a Xamarin Forms Shell app, and I also had the same issue, So what you can do is, Make the common properties Global as in make those properties in App.xaml.cs and mark them as static.
So when the User changes the property on settings change the App.PropertyName.
Then on the OnApearing method of homepage call a method on the ViewModel say LoadDataValues() and read the App.PropertyName and modify the UI as needed.
What this will do is just before the HomePage appears it will keep the UI of HomePage ready.
Let me know if you have further issues.
when is a view scope in an Domino XPage application lost by timeout, when the page is not accessed anymore? Is there a timeout? Or are they lost not until the session is closed (because of a logout or of the timeout)?
I know, that there is the server page persistence configuration in the Xsp Properties. But when is the scope lost, if you do nothing in the browser? You don't work in other tabs, so that there are not too much pages. (Is there an event listener for that, that allows me to print this out?)
Thanks in advance
AFAIK a viewScope object cannot live longer than the user's session. In addition it is bound to the current page's rendering for a given user.
This basically means that there are three options to kill a viewScope object:
move on to a different page
ask for a new rendition of the same page (like re-entering the same URL etc,; in fact this is the same as #1)
terminate the session by logging out, closing the browser etc.
You might want to try youself by building some test pages with a computed field bound to a viewScope variable; make sure that the variable is set through a button or the likes. Another option is to implement the Xpages debug toolbar available from openNTF.
A very simple explanation of all 4 scopes can be found here: http://www-10.lotus.com/ldd/ddwiki.nsf/dx/xpages-scoped-variables.htm, but you might be aware of that already.
It hadn't been doing that. Nothing seems to be triggered when the page is loading. What would trigger SSJS validation to run upon opening an xpage?
Your question is too vague to give an exact answer. I recommend watching the XPages Master Class. It will explain the JSF life cycle and show you how to use the XPages toolbox to diagnose your application to get the answer.
Check any partial refresh calls. Use firebug to view network traffic
See if any Ajax calls are being made when page loads. Also check
If you have any converters altering data that might trigger the validation
I have a number of sites using Kohana's session handler set to use database sessions. Everything works fine until I turn on Resource Tracking in Safari's Web Inspector. After enabling resource tracking, the page refreshes (normal), but then if I refresh the page twice I get logged out. From what I can tell, the session id/key changes therefore it has no session. Upon watching the storage/cookies area, I can see the session id cookie change immediately.
I haven't been able to reproduce similar behaviour in any other browser, including Chrome (Webkit).
Any ideas what might be causing this?
This appears to be fixed in Safari 5.1, so in other words, no longer an issue. Still love to know why it was happening (in case there's another issue), but for now it's resolved.
I'm writing an application in JSF 1.2 that has a session in a backing bean.
The biggest stability issue happens when the user refreshes the page (by pressing F5) or uses the backward arrow in the browser to go back.
I would like some 'smart' (knowledgeable) way to overcome this.
The most common exception I get is that after a refresh, the user will try to continue using the application and would get a:
java.lang.IllegalStateException - duplicate Id for a component
in the browser.
Thanks!
Don't bind physically different components by binding to one and same bean property.
If you want a smart (knowledgeable) way to overcome this, add seam to your jsf application. They have solved the backbutton problems in JSF