<br><div class="gmail_quote">On Fri, Feb 4, 2011 at 10:44 AM, Jason Lee <span dir="ltr"><<a href="mailto:jason@steeplesoft.com">jason@steeplesoft.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On 2/3/11 10:49 AM, Kito Mann wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
1. Should JSF implementations be making use of composite component metadata (like "type") at runtime to enforce the intentions of the composite component author?<br>
Yes, assuming this can be done without sacrificing performance.<br>
</blockquote>
<br></div>
There's the rub. I'd be surprised if we could do that without killing performance (which is already one of JSF's most common complaints), though I'd love to see this feature add/specified. We could only do it if the PROJECT_STAGE is set to development, which I think would be sufficient.<br>
</blockquote><div><br></div><div>That would be fine. It's definitely a development concern (assuming people test their apps before putting them into production...). </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<font color="#888888">
<br>
-- <br>
Jason Lee<br>
Senior Member of Technical Staff at Oracle<br>
<a href="http://blogs.steeplesoft.com" target="_blank">http://blogs.steeplesoft.com</a><br>
<br>
</font></blockquote></div><br>