I still don&#39;t understand why the composite component is not acting like a naming container. I mean, if I assign an id to the composite component:<br><br>&lt;p:edit id=&quot;username&quot;/&gt;<br><br>Then it just seems wrong to me that it isn&#39;t rendered in the output. However, if we are saying that the composite component must have:<br>
<br>&lt;div id=&quot;#{cc.clientId}&quot;&gt;<br>...<br>&lt;/div&gt;<br><br>(or something of the sort), then we need to highlight this point in big *bold* letters. Otherwise, every time a newcomer creates a composite component that he/she wants to update with Ajax, they are going to going through this trial and error lesson.<br>
<br>-Dan<br><br><div class="gmail_quote">On Sun, May 24, 2009 at 10:52 PM, Jim Driscoll <span dir="ltr">&lt;<a href="mailto:Jim.Driscoll@sun.com">Jim.Driscoll@sun.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
The only bizzare bit is where the absolute id didn&#39;t work - but that&#39;s explainable in a few ways.<br>
<br>
The basic technique - using #{cc.clientId}:subcomponentid to reference the rendered id in the ajax calls,  does not seem excessively hard to me.<br>
<br>
If you&#39;re doing ajax stuff in page, you need to know what the rendered id&#39;s are going to be.  The minute you start doing anything past hello world, you will anyway.<br>
<br>
If you disagree with this, having seen the basic demo, then obviously I&#39;m wrong, since I&#39;d say you&#39;re both more sophisticated than the target audience.  So please check that out (jsf-demo/ajax-switchlist), and let me know.<br>
<font color="#888888">
<br>
Jim</font><div><div></div><div class="h5"><br>
<br>
On 5/24/09 7:09 PM, Dan Allen wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hmmm, that seems really bizarre. Perhaps this is a bug in Mojarra but<br>
some chance. Could you distill this down to a basic use case and see if<br>
Ryan et al can make it a test in Mojarra. If there is a problem with the<br>
API, then it will be more clearly revealed.<br>
<br>
<br>
        Frankly, for JSF 2.1, I would like to see us go to an XPath-like<br>
        syntax (or jQuery) to find components because component IDs in<br>
        JSF just plain suck.<br>
<br>
<br>
    Yup, I agree wholeheartedly, but we need to make it easy to do Ajax<br>
    rendering across composite components for JSF 2.0. IMO, composite<br>
    components are by far the single most kickass feature of JSF 2, and<br>
    if they&#39;re crippled, we&#39;re gonna get some bad press.<br>
<br>
<br>
No doubt. We definitely can&#39;t overlook the foreground problem here.<br>
<br>
-Dan<br>
<br>
--<br>
Dan Allen<br>
Senior Software Engineer, Red Hat | Author of Seam in Action<br>
<br>
<a href="http://mojavelinux.com" target="_blank">http://mojavelinux.com</a><br>
<a href="http://mojavelinux.com/seaminaction" target="_blank">http://mojavelinux.com/seaminaction</a><br>
<a href="http://in.relation.to/Bloggers/Dan" target="_blank">http://in.relation.to/Bloggers/Dan</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&#39;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&#39;t hesitate to resend a message if<br>
you feel that it did not reach my attention.<br>
</blockquote>
</div></div></blockquote></div><br><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>
<a href="http://in.relation.to/Bloggers/Dan">http://in.relation.to/Bloggers/Dan</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&#39;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&#39;t hesitate to resend a message if<br>
you feel that it did not reach my attention.<br>