The current LogicalViewProvider.findPath definition does not allow to reliably return nodes when nodes are created asynchronously (Children.create(XXX, true)). Not even with Children.getNodes(true). The reason for this is because Children.getNodes(true) waits only for the node keys to be created and not necessarily for nodes. Note that Children.getNodes cannot (or rather should not) be fixed to wait for the node creation as it would be extremly dead-lock prone. 

Another reason for the new API is that if nodes are slow to be created (which is probably the reason why they are asynchronously created in the first place), waiting for this method might block the UI, which is not user-friendly.

My proposal is that LogicalViewProvider (or rather a new LogicalViewProvider2 to preserve backward compatibility) should provide a findPath method which notifies the caller through a passed callback. Given that asynchronous calls can be expected to take some time, a cancellation mechanism should be used to allow the asynchronous call to be canceled.

Note that this API might imply that Children should have an asynchronous way to retrieve its children. Otherwise, it could be very inconvenient to implement the new LogicalViewProvider interface.