@Gerhard: Thanks for the hint. I followed your migration demo on os890 github. Very helpful!
I did a lot of research and found that difference for our button navigation. They are mostly commandButtons and within the action method they use a ViewNavigationHandler and ViewConfig to navigate. I forked deltaspike, created a branch and modified the jsf-playground example, so it is now showing the intermediate page with the loading text. For my local tests I used Firefox 39 where I don't see the flickering, but it occurs on Google Chrome 44. IE11 is causing many exceptions on postback links and buttons I tested with Tomee and Glassfish profile, both same behavior. Here is the Fork/Branch link: https://github.com/mlachat/deltaspike/tree/ds-1.4.2-WindowHandling In our application, running on WAS 8.5.5.4, even Firefox is not working and shows the loading page. Best regards, Markus -----Ursprüngliche Nachricht----- Von: Gerhard Petracek [mailto:[email protected]] Gesendet: Mittwoch, 29. Juli 2015 22:25 An: [email protected] Betreff: Re: WindowClientMode shows white Loading... Page hi markus, fyi (since you migrate from codi): please don't forget to add the component ds:windowId [1] to your page(-template). (codi adds such a component automatically to the page, but with ds you need to do it manually.) regards, gerhard [1] http://deltaspike.apache.org/documentation/jsf.html#Configuration http://www.irian.at Your JavaEE powerhouse - JavaEE Consulting, Development and Courses in English and German Professional Support for Apache MyFaces, DeltaSpike and OpenWebBeans 2015-07-29 22:06 GMT+02:00 Markus Lachat <[email protected]>: > I tried both versions of DS (1.3.0 and 1.4.2) and also changed the > playground to use type-safe navigation, the same way my application does. > For my application the window handler stores away the site on most > buttons and links, but not for all. Playground is fully working now, I > don't see the loading text there anymore. Really strange I saw it before. > > I am now trying to find the difference between the links and buttons > on playground and my application. I will let you know, thanks for your > help so far! > > -----Ursprüngliche Nachricht----- > Von: Thomas Andraschko [mailto:[email protected]] > Gesendet: Dienstag, 28. Juli 2015 16:00 > An: [email protected] > Betreff: Re: WindowClientMode shows white Loading... Page > > FYI: > Just tried it in the playground and it works fine e.g. when you open > http://localhost:8080/ds/views/windowhandling/clientwindow/test.xhtml > and click on "GET Link". > > The Problem is probably the Post-Redirect-Get as only the onclick of > links will overwriten. If you use a button it might not work. > Could you please post a sample? > > > 2015-07-28 15:42 GMT+02:00 Thomas Andraschko > <[email protected] > >: > > > Hi, > > > > which version do you use? > > I refactored many things in the last release. Can you also verify > > this e.g. with 1.3.0? > > > > 2015-07-28 15:39 GMT+02:00 Markus Lachat <[email protected]>: > > > >> Hi, > >> > >> I migrated from CODI and everything went fine so far. I am using > >> TypeSafe Navigation and Navigation Mode is set to redirect and > >> viewParams is also included. So the application follows mostly the > >> Post-Redirect-Get Pattern (as far as I understood). > >> > >> However I am seeing the white intermediate page, displaying the > >> loading... text. The documentation states a HTML5 enabled browser > >> caches the screen, css etc. to the localstorage and the flickering > >> effect would be gone. > >> > >> I also tested the playground app, where I see the same effect. The > >> main application runs on Websphere and the playground testing app > >> on > TomEE. > >> > >> Any suggestions? What am I doing wrong? > >> > >> Kind regards, > >> Markus > >> > > > > > >
