So, here's one other thing that came up at JSFDays -- the fact that composite components (like Facelet compositions) don't restrict which attributes can be used. This is fine for Facelet compositions, but since composite components can define specific attributes, it makes sense to give component authors the ability to restrict page authors to those attributes.<br>
<br>I think the easiest way to handle this from a component author's perspective would be to add an attribute to the <component:interface> tag:<br><br><component:interface restrictAttributes="true"><br>
<component:attribute name="name" required="true"/><br> <component:attribute name="size"/><br></component:interface><br><br>So, in this case, this component would _only_ accept the name and size attributes, and the runtime would throw an exception if another attribute were used. An IDE could also complain when someone tried to use a different attribute.<br>
<br>Thoughts?<br clear="all">---<br>Kito D. Mann -- Author, JavaServer Faces in Action<br><a href="http://twitter.com/kito99">http://twitter.com/kito99</a> <a href="http://twitter.com/jsfcentral">http://twitter.com/jsfcentral</a><br>
<a href="http://www.virtua.com">http://www.virtua.com</a> - JSF/Java EE consulting, training, and mentoring<br><a href="http://www.JSFCentral.com">http://www.JSFCentral.com</a> - JavaServer Faces FAQ, news, and info<br>+1 203-404-4848 x3<br>
<br>Public JSF Course in NYC (April 21st-24th): <a href="http://www.regonline.com/jsf-course">http://www.regonline.com/jsf-course</a><br><br>