Drag and drop (or copy) OAR behavior. Right now if an OAR is dropped the FileSystemOARHandler checks to see if it has already been installed. If it has not been installed it will be installed and (based on it's OAR-Activation manifest property) be deployed. If the OAR has already been installed, the FileSystemOARHandler will check if the OAR has been updated. If the OAR has been updated it will overwrite the earlier installation and be deployed if it is not already deployed. If it has not been updated no action is taken, other than logging a message.

After sleeping on this I propose the following: If an OAR is dropped (copied) for deployment, the FileSystemOARHandler will always install the OAR. If the OAR has not been deployed (and based on it's OAR-Activation manifest property), will be deployed. If it is already deployed, the deployed opstring will be updated.