Description
In CompositeComponentDefinitionTagHandler, there are some lines that store the Location object inside the composite component, that is used later for EL resolution (CompositeComponentELUtils.LOCATION_KEY), but each time the algorithm pass over that part when the view is refreshed, the same value is stored over and over again. With as simple check we can avoid that and minimize the state size when composite component are used.