<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div class="h5"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
Dan -<br>
<br>
I think that you are most familiar with the current f:validateBean implementation. Assuming that you are okay with the proposal, would you be willing to take a look at what we do for f:ajax and maybe sync up with Ryan to discuss what it would take to convert this over to the f:ajax strategy? The f:ajax approach is fairly simple:<br>
<br>
- When we encounter f:ajax, we create an AjaxBehavior and push it onto a stack.<br>
- When we encounter a ClientBehaviorHolder component that can accept the AjaxBehavior instance, we create/configure a new AjaxBehavior instance and attach it to the ClientBehaviorHolder<br>
- When we reach the end of the f:ajax tag, we pop the AjaxBehavior stack.</blockquote></div></div></blockquote></div><br>Absolutely. I can tell you that implementation the <f:validateBean> as a nested tag was a pain to developer. It's much simpler to use the wrapping approach because you know what you have to apply going into the subtree. We spent the time on the nested tag approach because we were under the impression that it would be more straightforward for the developer. But clearly there are implications with that solution that cannot be ignored and you are right in wanting to align it with <f:ajax>.<br>
<br>Ryan, let me know if you need a hand.<br><br>-Dan<br clear="all"><br>-- <br>Dan Allen<br>Senior Software Engineer, Red Hat | Author of Seam in Action<br><br><a href="http://mojavelinux.com">http://mojavelinux.com</a><br>
<a href="http://mojavelinux.com/seaminaction">http://mojavelinux.com/seaminaction</a><br><br>NOTE: While I make a strong effort to keep up with my email on a daily<br>basis, personal or other work matters can sometimes keep me away<br>
from my email. If you contact me, but don't hear back for more than a week,<br>it is very likely that I am excessively backlogged or the message was<br>caught in the spam filters. Please don't hesitate to resend a message if<br>
you feel that it did not reach my attention.<br>