Hi,
I am using myfaces 1.1, icefaces 1.8.1 on WAS 6.0
The controller (backing bean) action methods handle RuntimeException from the
service layer. Depending on the exception an exception handler will put an
appropriate message into FacesContext.
For that I have created a utility method:
Hi,
for clearification: does the click on the command button take place
AFTER the page with the error messages was rendered? Because if it is
so, this is the expected behavior. The messages in the FacesContext are
only available for the current request, which is the one producing the
error.
Hi Madhav,
the livecycle did not depend on messages in the context. To prevent
executing actions and direct skip to renderPhase you need to call
FacesContext.getCurrentInstance().renderResponse();
e.g. in your putMessage() method.
Regards,
Volker
2010/1/20 Madhav Bhargava
True, you are right.
The problem was that the first request goes as an AJAX request submitting on a
part of the form. If there are errors, messages are shown. Now the user clicks
on any other control which submits the rest of the page barring the one which
was previously submitted. That caused
Hi Volkar,
Thanks for your response. I will add that to the method so that it does not
have to be explicitly done by the developers in their action methods.
From: weber.vol...@googlemail.com [mailto:weber.vol...@googlemail.com] On
Behalf Of Volker Weber
Hi Madhav,
the livecycle did not
5 matches
Mail list logo