I noticed this when using the Trinidad components. I had to add this in web.xml to fix it :
<context-param>
<param-name>
org.apache.myfaces.adf.CHECK_FILE_MODIFICATION
</param-name>
<param-value>true</param-value>
</context-param>
This is supposed to add some overhead in terms of performance, but I did not notice anything significant. I am not aware of a similar parameter using Tomahawk.
- Anil.
-----Original Message-----
From: Michael Heinen [
mailto:[EMAIL PROTECTED] ]Sent: Wednesday, November 08, 2006 12:13 PM
To: MyFaces Discussion
Subject: 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
