<br><div class="gmail_quote">On Mon, May 25, 2009 at 1:39 AM, Jim Driscoll <span dir="ltr"><<a href="mailto:Jim.Driscoll@sun.com">Jim.Driscoll@sun.com</a>></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;">
<div class="im">On 5/24/09 8:39 PM, David Geary wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
And that id is *exactly* what <f:ajax> says it cannot find. It's in the<br>
page, but <f:ajax> cannot find it?!?<br>
<br>
My guess is that <f:ajax> is evaluating the id before the page is<br>
completely constructed, and therefore, it doesn't find it, but that's<br>
just a WAG on my part.<br>
<br>
So, if this is not correct:<br>
<br>
<f:ajax render="#{cc.parent.clientId}:image"/><br>
<br>
Then how do I access the image in the parent (map) component?<br>
<br>
It seems to me that I'm using <f:ajax> correctly, but I'd be happy to be<br>
told otherwise.<br>
</blockquote>
<br>
<br></div>
It's late, but yes, that looks correct, and yes, your guess sounds correct. Could you file this as an impl bug?<br>
<br>
Now, we do need to fix that as a bug, but I must argue that your use case represents bad practice. Your component is using ajax inside a component to modify the using page. That's difficult to maintain, and I suspect it will lead to obfuscated code quite easily. I'd instead argue that if you are going to have one component modify another, you should either group them into one composite, or, have the ID of the component you act upon passed in as an attribute (say "for="?)</blockquote>
<div><br>Very good point. You should definitely be parametrizing the id anyway. <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
<br>
Of course, that second usage suggestion opens up another hole in the cc api - the lack of ability to do name resolution. Though if/when we get method parameters, then cc.findComponent will work, I guess. Though I've been saying that for a pretty long time now, I should check on when we're getting those method params...</blockquote>
<div><br>Apparently in Java EE 6 under the auspices of JSP 2 MR1. We should check with the Java EE 6 EG on this one.<br><br>-Dan<br></div></div><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.relationto/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'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>