Hi
The problem basically is there is no way to detect which
javax.faces.ViewState hidden fields belongs to a specific window or
view from the client side (javascript). To solve this it is necessary
to pass a marker, and use it to find all related
javax.faces.ViewState hidden fields and update
After talking to our testers it seems as though once the rollback happens
this occurs on pages with and without AJAX calls on them.
We are trying to reproduce again as we speak.
Thanks,
Paul Nicolucci
Hi Paul then the issue will be harder to nail down.
The problem I was referring to is only client side based and can only
occur in multiple forms.
I doubt your problem has anything to do with the problem I was referring
to, at least not directly, there must be at least a second part to this
Before going further, does this problem also occur in a non ajax case or
is it entirely ajax related.
Werner
Am 05.01.12 08:24, schrieb Werner Punz:
Hi Paul then the issue will be harder to nail down.
The problem I was referring to is only client side based and can only
occur in multiple
Hi,
I had similar problem once and it was caused by combination of unhandled
exception + ajax-error.
When exception occurs in partial/ajax request/respose (for example SQL
exception), JSF send back to client XML with following structure:
partial-response
error
error-name.../error-name
@Martin,
I will try the suggestion above to reproduce the issue by throwing a
exception in garageSaleJSFActions.updateCart or introducing an artificial
rollback exception.
If I can recreate consistently I will be able to fix it fast.
@Mark,
I am also investigating my session persistence settings
Werner and Michael,
I will employ the workaround suggested to see if it helps.
I do have a mix of f:ajax and h:form on my facelet. showShoppingCart.xhtml
h:commandButton type=submit value=Update
styleClass=commandExButton id=updateButton
action=#{garageSaleJSFActions.updateCart}
f:ajax
Not really, the ViewExpired exception just means that
the current ViewState cannot be found anymore in the view history.
If you navigate
to a new page, you basically get a Tabula Rasa aka a new
ViewState.
Either way if it is the JSF Ajax problem, the javascript workaround
definitely will fix
...@gmail.com
To: users@myfaces.apache.org
Cc:
Sent: Thursday, December 29, 2011 10:49 PM
Subject: Re: How to troubleshoot ViewExpiredException ?
Not really, the ViewExpired exception just means that
the current ViewState cannot be found anymore in the view history.
If you navigate
to a new page
Dear all,
We have run into an issue with our application in production wherein once a
database rollback occurs, our application state somehow gets messed and we
repeatedly keep seeing ViewExpiredExceptions like so ...
[12/24/11 3:51:52:301 EST] 03b3 SystemErr R
Do you use multiple forms in conjunction with JSF ajax?
Werner
Am 28.12.11 18:30, schrieb Rohit Kelapure:
Dear all,
We have run into an issue with our application in production wherein once a
database rollback occurs, our application state somehow gets messed and we
repeatedly keep seeing
11 matches
Mail list logo
