Hi Stephan, well, the reason for that is to be found in the JSF-lifecycle.
On a post-back, all 6 phases are executed - on the first request, only the first and the last are executed. As when the session is empty, we're talking about a "first" request, your action won't be executed at all. Option: you could create a phase-listener which executes an action based on a certain parameter in the request being set. regards, Martin On 11/21/06, Strittmatter, Stephan <[EMAIL PROTECTED]> wrote:
Has anybody any idea? I have still this problem. Thanks, Stephan -----Ursprüngliche Nachricht----- Von: Michael Heinen [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 8. November 2006 18:13 An: MyFaces Discussion Betreff: RE: First action does no call to backing bean I have the same problem on my login screen. I have a default login screen with user/password input fields and a login button. When the web session has terminated and the user clicks the button then the action is not executed and the screen is displayed again. The second button click is successful. This is really annoying in some cases. Any help is highly appreciated. Michael -----Original Message----- From: Strittmatter, Stephan [mailto:[EMAIL PROTECTED] Sent: Mittwoch, 8. November 2006 17:21 To: MyFaces Discussion Subject: First action does no call to backing bean Hello, I use MyFaces 1.1.5-snapshot for current development of my application. Now I found a problem, that always the first action within a session called through a commandButton is not passed to the associated backing bean. I have no idea where to search for this problem. Has anybody any hint? Thanks in advance, Stephan
-- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
