Page History

{scrollbar}

See \[jsr-344-experts\] [should really a composite component requires NamingContainer interface?|http://java.net/projects/javaserverfaces-spec-public/lists/jsr344-experts/archive/2011-07/message/2] for details

In theory, a "non explicit" requeriment for a composite component class is it should implement NamingContainer interface. Note I said
"non explicit", because in practice there is nothing on JSF 2.0 spec that enforces that.

...

Note this hack becomes useful when you have facelets 1.1.x pages and you want to convert them to composite components, so if you are creating new composite components it is better to keep them as NamingContainer instances, unless by some reason (like in the panel problem) you need the root component not to be a NamingContainer.

See \[jsr-344-experts\] [should really a composite component requires NamingContainer interface?|http://java.net/projects/javaserverfaces-spec-public/lists/jsr344-experts/archive/2011-07/message/2] for more information.

{scrollbar}