Hi<br><br>That's cool. Just one minor comment. Looking the documentation I saw UIData.getClientId still return the id with the rowIndex added.<br><br>In the mails to this list with this subject:<br><br>[jsr-314-open] Ajax inside a DataTable<br>
<br>It was told it is better to change the behavior of UIData.getClientId, to it does not include the id and instead set this behavior on UIData.getContainerClientId. This requires some small changes on UIData.invokeOnComponent (call UIData.getContainerClientId instead UIData.getClientId) and other methods, but it seems the way to go. Could you please consider this change to be included in Rev A? <br>
<br>I created a spec issue here:<br><br><a href="https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=865">https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=865</a><br><br>Thanks a lot for you attention. I'll keep an eye if this is finally include in JSF 2.0 Rev A. I already committed this change on myfaces but if it is not accepted or deffered by some reason to 2.1 I'll revert those changes.<br>
<br>best regards,<br><br>Leonardo Uribe<br><br><div class="gmail_quote">2010/7/10 Ed Burns <span dir="ltr"><<a href="mailto:edward.burns@oracle.com">edward.burns@oracle.com</a>></span><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Hello Experts,<br>
<br>
As mentioned at the 20100707 Expert Community meeting, here is the release<br>
candidate 1 of the JSF 2.0 Rev a specification. [1]. There really isn't<br>
any room for modifications for 2.0 Rev a at this point, but if you find<br>
something major, please let me know. Otherwise, please continue to log<br>
issues in the javaserverfaces-spec-public issuetracker.<br>
<br>
Please keep in mind this description of 2.0 Rev a when reviewing it,<br>
taken from the javaserverfaces-spec-public home page.<br>
<br>
This effort will include work that does not require any change in<br>
behavior of the implementation (including any signature changes) or<br>
TCK. This work will be limited to spec edits. This work will be<br>
conducted under the JCP Minor Revision process. Because there are no<br>
implementation changes, no new release of the Reference Implementation<br>
(RI) or Test and Compatibility Kit (TCK) will be produced to accompany<br>
2.0 Rev a. The existing JSF 2.0 RI and TCK will be sufficient for this<br>
purpose.<br>
<br>
For my money, the more interesting release is 2.1, which is currently in<br>
progress.<br>
<br>
Thanks,<br>
<br>
Ed<br>
<br>
[1] <a href="https://javaserverfaces-spec-public.dev.java.net/servlets/ProjectDocumentList?folderID=12309&expandFolder=12309&folderID=12309" target="_blank">https://javaserverfaces-spec-public.dev.java.net/servlets/ProjectDocumentList?folderID=12309&expandFolder=12309&folderID=12309</a><br>
<font color="#888888"><br>
--<br>
| <a href="mailto:edburns@oracle.com">edburns@oracle.com</a> | office: +1 407 458 0017<br>
| homepage: | <a href="http://ridingthecrest.com/" target="_blank">http://ridingthecrest.com/</a><br>
</font></blockquote></div><br>