This content has been marked as final.
Show 2 replies
-
1. Re: a4j:commandLink - Bean's action not fired
1kaa Jun 26, 2007 5:14 AM (in response to snew2k5)I have a similar problem with commandButton. Actions are not called. This affects the 3.0.1 release of RichFaces. The June 1 snapshot build works as expected.
-
2. Re: a4j:commandLink - Bean's action not fired
1kaa Jun 26, 2007 5:49 AM (in response to snew2k5)Oh, and as noted elsewhere, there is a compatibility issue with versions of Tomahawk.
For the record, here's what works for me:
MyFaces 1.1.5
Tomahawk 1.1.3
Tomahawk Sandbox 1.1.3 snapshot (2006/05/26)
Richafaces 3.0.1 snapshot (2006/06/01)
If I change either RichFaces or Tomahawk to use later releases, then the action on the a4j command button no longer fires.
If I change the JSF code to use a h:commandButton with a4j:support then the action is fired, but I get JavaScript errors in the Tomahawk hidden field clear script.
:-)