Is it possible to dispense with having to type &quot;#compositeComponent.attrs.&quot; in the implementation sections of composite components? It&#39;s cumbersome. Besides, Facelets custom tags let you access attribute values with their simple names, for example you could use a Facelets tag like this:<br>

<br>&lt;mytags:planet name=&quot;mercury&quot; image=&quot;#{resource[&#39;images:Mercury.gif&#39;]}&quot;/&gt;<br><br>and in the implementation of the planet tag, you can do this:<br><br>&lt;h:graphicImage style=&quot;border: none&quot; <br>

  value=&quot;#{image}&quot;/&gt;<br><br>With a JSF composite component, you have to do ...value=&quot;#{compositeComponent.attrs.image}&quot;. Maybe I&#39;m missing something, but it doesn&#39;t seem to be too much of a
technical feat to remove the need to type compositeComponent.attrs (a variable resolver that searches
compositeComponents.attrs, as necessary?)<br><br>It seems weird that we&#39;re taking a step backwards in this respect, even as we move forward from Facelets tags to more feature-rich composite components.<br><br><br>david<br>

<br>