E Armitage wrote:Generally, JSF (these days) is best when you are taking advantage of the automatic property binding to backing beans as you would in CRUD pages. You're better off using stateless views for dashboard type pages with data fetched via AJAX rather than trying to fit that into JSF's bindings. You can still use JSF for the page (to take advantage of templating or for uniformity with other pages) but rather use restful services for getting the data from the server and use JQuery to fetch the data and set it on the page controls.
Tim Holloway wrote:Of course, you could hack it by stacking multiple 1-row tables to look like a multi-row table. I've pulled stunts like that on pre-JSF HTML apps. Eek.
XDDD In my experience, sanity usually is the opposite of reality.
Tim Holloway wrote:Speaking of unrealistic expectations, did I ever mention the project they gave me back in my mainframe days? It consisted of a 7-level report done multiple ways. We estimated that each daily run was going to consume 2 and a half 2500-sheet boxes of fanfold paper and propably no more than a page or 2 of the report would ever be actually looked at at any given time. Fortunately, we managed to persuade the users in the direction of sanity.
Akaine Harga wrote:..The apps look nice, they require little coding, but they are slow. And with the Internet connection becoming faster each year people will start complaining more and more..
Akaine Harga wrote:..
You mean I should forget about property binding and manually use jQuery for data fetching and view updates? And that without mentioning the stateless views. But wouldn't that multiply the required time for coding, code complexity in several times and render the best JSF's feature (variable binding) just useless? I'm not entirely against the idea, I just need time to get used to it, I guess.
Akaine Harga wrote:
Actually, guys, one of the purposes of my post was exactly this:
Is JSF (or any other "automated" WebMVC) good for heavy views? Or am I actually hitting the limits here? I was considering to move to JavaFX8 for some time by now. As far as I understand I won't have any of these problem there. Or even forget Java completely and move to .Net SOA based apps. Because the idea of spending weeks of jQuery coding for a relatively simple functionality doesn't appeal to me as the most optimal (time/cost) solution.