hi yogi,
i tested the mentioned scenario with the archetype apps #1 and #2.
i changed the following:
1) dependencies (update to v1.2.6)
2) added immediate command buttons
-> everything worked fine!
-> could you please provide more details or a link to a sample app.
regards,
gerhard
http://www.irian.atYour JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
2009/6/22 Karma Yogi
<karmayogi31@...>
All,
I have been using the immediate attribute on all my cancel command buttons
since MyFaces 1.1 and have had no issues with its usage. I am attempting to
upgrade to Myfaces 1.2.6 and suddenly all my cancel command buttons do not
work as intended. This is the behavior that I notice.
1) All required validations of fields fire the moment I click the
"immediate" tagged btn.
2) The listener for the cancel btn is never reached.
I cannot be missing anything in the basic usage itself because this was
working perfectly before the upgrade. So what else could I be missing ? Or
is this a bug in this version ? Some clarity on this from the gurus would be
appreciated.
FYI I have already read the wiki on using the immediate attribute at
apache.org and I am using the same techniques mentioned there
Ciao
Yogi
--
View this message in context: http://www.nabble.com/MyFaces-1.2.6-immediate-attribute-on-command-button---required-validation-tp24151328p24151328.html
Sent from the MyFaces - Users mailing list archive at Nabble.com.
