-
1. Re: Should a4j:ajax behavior act as ActionSource? (RF-7827)
alexsmirnov May 18, 2010 10:41 AM (in response to ilya_shaikovsky)a4j:support has been made as ActionSource to support particular use case: perform navigations on AJAX requests. Using only action component properties seems not enough because it can be used with non-action components like SelectOneMenu or even layout components like tables or panels ( onrowmouseclick in the table, for example ).
I think that feature makes sense for JSF 2.0 behavior also. It also would be helpful for migration from RF 3.x to 4.0
P.S. With behaviors, I even thought about some kind of "submit" one that can submit form on particular event and lets developer to use standard navigation on non-command components. Such behavior would be complimentary for a4j:support.
-
2. Re: Should a4j:ajax behavior act as ActionSource? (RF-7827)
ilya_shaikovsky May 18, 2010 11:09 AM (in response to alexsmirnov)a4j:support has been made as ActionSource to support particular use case: perform navigations on AJAX requests.
but support was much limited (redirect or using a4j:include)
And mainly the guys just put their business logic on entered values processing to action.
Using only action component properties seems not enough because it can be used with non-action components like SelectOneMenu or even layout components like tables or panels ( onrowmouseclick in the table, for example ).
It's not really convenient but possible for now also by using navigation handler directly in ajax listener.
P.S. With behaviors, I even thought about some kind of "submit" one that can submit form on particular event and lets developer to use standard navigation on non-command components. Such behavior would be complimentary for a4j:support.
So maybe create separate "action" behavior which will have two modes and will be designed for navigation?
P.S. I'm not completelly against but just wants to get all your opinions - if this additional functionality looks native for just ajax submission behavior