YComponentInfo and Facelet are of different nature.
However the similarity is that both are representing a piece of the view (xhtml)
Facelet autodetect changes.
In case YComponentInfo would do so, it could be used much better
Currently it's used for on the fly validation and default component instantiation (via ID)
But every YCOmponentInfo instance which is requested from the YComponentRegistry
doesn't recognize xhtml changes.
HtmlYComponent avoids this lack by creating a new YComponentInfo everytime.
In case reloading would be working many members would be useable e.g.: