If the same Composite Component is used inside itself, e.g. as child of an ui:include that is included in the Composite Component, an StackOverflow happens, if an EL Expression is refering CC interface attributes.
The use case is a CC to include a facelet, given by name. If the included facelet uses the same CC to include another facelet, "CompositeComponentELUtils.getCompositeComponentBasedOnLocation(..)" does always find the same CC, which leads to an endless loop.
Please see the attached file for an example of the issue.