Am 07.09.10 13:26, schrieb Mark Struberg:
Hi!
We have a page which renders a confirmation dialogue area with f:ajax and this
confirmation dialogue has a h:commandButton.
Since our view restoration may take a bit it happens that the user might click
fast enough on the commandbutton while the ajax request is still on the server.
Thus we might have 2 parallel requests on the same @ViewScoped bean. This is
even more troublesome if we use CDI @ConversationScoped beans.
We looked at the jsf.js and it seems that although concurrent f:ajax requests
get queued the submit via the commandButton hits the server unqueued.
Is this behaviour in sync with the spec?
There is a workaround to also only use f:ajax with commandButtons, but since I
have to use this all the times it could be easier to queue submits also.
LieGrue,
strub
I will investigate it the first request should get through unqueued the
second one has to go into the queue and wait while the first one is
executing that is the expected behavior, let me check if we have a
queuing error there.
There should be no request issued against the server while another one
currently is on the server.
Werner
