#3316 switch to ajax request

[markusweigelt]

Fixes #3316

[matthias-ronge]

I don’t understand what is happening here, but with regard to program style, etc., that is correct

[solth]

@matthias-ronge Primefaces tags use Ajax per default (instead of vanilla JSF tags). Without using Ajax, the commadLink reloads the page (because the corresonding action returns "null" or is "void") which results in the "growl" message and the message area above the main content being updated with the message text. By using Ajax instead, the page reload is prevented and the message is only displayed in the specifically updated message area above the main content.

This solution is the same to what I did in #4615

[matthias-ronge]

Yes, I am not deep into this, but I agree.

[markusweigelt]

@solth I saw the issue and adapted it. ;) In my opinion, my fix is a workaround rather than a solution. Because in some cases an ajax variant will not be possible.

In the future, we should choose between output in flag/sticky-notification or top header message levels.

In order not to display flag/sticky-notifications in a disruptive way, we should update prime face cause lifetime of flag is not changeable. "life" attribute of growl does not work.