FS#77 - FormCommand incompatible with ADF Faces Dialog Framework
Opened by Strict Standards: array_map() expects parameter 1 to be a valid callback, non-static method Filters::noXSS() should not be called statically in /home/commitcons/tracker.commit-consulting.com/includes/class.tpl.php on line 281 Wilfred van der Deijl (wvanderdeijl) - Strict Standards: Non-static method Filters::noXSS() should not be called statically in /home/commitcons/tracker.commit-consulting.com/includes/class.tpl.php on line 613 Tuesday, 08 July 2008, 08:58 GMT-7
A FormCommand can invoke a ADF Faces Dialog navigation by simply specifying "dialog:outcome" as the action. If the faces-config.xml has been setup to use a navigation case with a name "dialog:outcome", the ADF Faces Dialog Framework will kick in.
Eventually, the user returns from the dialog, for example by pressing the following button:
This invokes JSF navigation to the original OraFormsFaces page. However, it seems like the ADF Faces Dialog Framework tries to deliver a ReturnEvent to the FormCommand component that initiated the dialog. This in interpreted by the FormCommand component as if the user activated the FormCommand component, so the FormCommand component queues an ActionEvent which causes another invocation of the same dialog. In the end, the user stays in the dialog and it seems like nothing is happening.
We need to see if a FormCommand component can be made aware of the ReturnEvent and not invoke its normal action, but perhaps a ReturnListener. We need to make sure we can do this without introducing a dependency of ADF to OraFormsFaces.