JSF: Actions calls are delayed?

I'd say your browser is having a hard time with the "lousy" javascript generated by JSF. Did you measure performances with different browsers? I suggest seeing if chrome for example goes faster.

Thanks for the guess, it takes as long in IE too. I'll check out if it's faster in Chrome, but I doubt it. The form isn't very sophisticated/big either.

:( – geeehhdaa May 24 at 12:13.

The only feasible explanation I can think of is that you're doing expensive business logic inside a getter method instead of in the bean's constructor or any other event method which is called only once when necessary. Getter methods are intented to only return some prepopulated bean property or at highest do lazy loading, not to do expensive business logic like connecting a DB, copying 1000 rows into Java's memory, etcetera. Getter methods can be called more than once during a JSF request, which grows exponentially when the call is made inside an iterating component like or is been used in rendered attribute.

JSF/EL won't cache results of getter methods on a per-request basis or something since a normal getter call is prarticularly cheap. See also: Why JSF calls getters multiple times.

The getters should not be the problem. I noticed it takes ~ 5 seconds for Firefox to render the source code of the page, even though it's only ~ 250 lines. It's way faster for every other xhtml-file.

I guess that means that something's wrong with the generated html-code? Is there any way I can find out what's wrong? – geeehhdaa May 31 at 14:52.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.