Revision 1712584

SLING-5243 : adding a retry-loop for the newly-introduced exception handling around establishedView.matches. Reason for this: looks like during testing you can run into a race-condition where the establishedView is just being created and only half visible - in that case this matches() throws an Exception even though the view will just be there - so doing a 5x500ms retry loop should handle this case. And since this is probably only a testing artifact, it shouldn't have any influence on real usage