vApps in VMs and Templates inventory are being treated as single entity, moving it's component VM will move it's location completely. One of the use case of VM is to manage a multi-tier app in a single container, in that case I would be more interested move whole multi-tier app together, not one of the component.
while Resource Pools are not even visible in VMs and Templates Inventory so VMs which are child object of Resource pools in Host and Cluster inventory are free to move around across different folders in VMs and Templates inv. view.
so yes, you are right. You cannot expect vApps and Resource pools to be giving similar behaviour in VMs and Templates Inv. view
As per my understanding vApp and Resource Pools are altogether different objects.
vApp is used for multi tier applications and their starting order ,
Resource Pool is for hierarchical (Parent/Child) approach to provide resources to VMs underneath.
I think we can't search VMs in VM-Template view those are part of vApp object. only Group name will be listed.
you are correct about Resource Pools.
Thanks both of you for your explanations.
I guess I now have to rearrange my VMs so that there will be no confusion between Folders, vApps and Resources Pools.