In ConnectedAssetAdministrationShellManager, when deleting the AAS or SM it automatically tries to delete the corresponding AAS/SM from the registry as well, but if the AAS/SM has already been already removed from the registry then it would throw an exception.
As the AAS server (v1.4.0) now unregisters the deleted AAS/SMs automatically from the registry, the deletion would throw an exception.
We observed this issue in basyx-examples, while upgrading the AAS-Server to 1.4.0.
In ConnectedAssetAdministrationShellManager, when deleting the AAS or SM it automatically tries to delete the corresponding AAS/SM from the registry as well, but if the AAS/SM has already been already removed from the registry then it would throw an exception.
As the AAS server (v1.4.0) now unregisters the deleted AAS/SMs automatically from the registry, the deletion would throw an exception.
We observed this issue in basyx-examples, while upgrading the AAS-Server to 1.4.0.
This PR corrects the behavior.
Signed-off-by: Mohammad Ghazanfar Ali Danish ghazanfar.danish@iese.fraunhofer.de