No polling with ProgressMonitorDialog and deployed application [message #1693883] |
Wed, 29 April 2015 06:36 |
Frank Jakop Messages: 8 Registered: July 2012 |
Junior Member |
|
|
We just migrated to RAP 2.3 and encountered a very strange behaviour with applications deployed to Tomcat.
When we invoke a Runnable with ProgressMonitorDialog (fork=true) we normally see GET-requests from the client to check if there was a change in the progress and then update the UI (see from-eclipse-with-m2e-wtp.png). This works fine using Tomcat from within Eclipse via m2e-wtp.
When we deploy the very same application in a standalone Tomcat (same version, same JRE) and start the identical Runnable, the application freezes, no progress is displayed. Looking at the requests, we see that the GET-requests are missing. (see deployed-in-tomcat.png)
We also notice a different origin of the according POST-requests, the working one comes from rap-client.js, the erroneous from DropDown.js, but that might be because we started the deployed variant with -Dorg.eclipse.rap.rwt.developmentMode=true for the sake of non-minified javascript.
When the ProgressMonitorDialog freezes, we can trigger a POST by moving the dialog with the mouse. Let's say the Runnable would call ProgressMonitor.worked() 3 times, we had to move the dialog three times for watching the progress bar increase and the dialog to finish.
Has anyone a clue what's going on or where to investigate further?
|
|
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03233 seconds