+1.<br><br>Also...<br><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;"><br>
1. The user must recognize that the component in question is a composite component and code the expression differently. While at the moment it is fairly easy to determine whether a particular component is a composite or not (by looking at the namespace declaration), I think that we should strive to blur these lines rather than reinforce them.</blockquote>
<div><br>Exactly. We don't want the page author to start discriminating between the implementations of a component. That's dangerous. <br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Leaving aside questions of how we might implement my preferred behavior for the moment... Does anyone have comments on which behavior makes sense from a spec/end user perspective?<br><font color="#888888">
<br></font></blockquote><div><br>The general goal should be to make composite components as indistinguishable from formal Java-developed components as possible.<br><br>-Dan</div></div><br>-- <br>Dan Allen<br>Senior Software Engineer, Red Hat | Author of Seam in Action<br>
Registered Linux User #231597<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://www.google.com/profiles/dan.j.allen">http://www.google.com/profiles/dan.j.allen</a><br>