I am not able to create new Datasource in EAP5 server if it uses the same name as Datasource which existed before but was already deleted.

The cause of this behaviour is that *.xml file remains in deployment directory of EAP instance even though JON and jmx no longer knows about it.



Steps to reproduce:

1 - create through JON ui new Datasource (ds type doesn't matter in this scenario) for EAP5.
2 - After successful creation delete it. 
3 - try to create new datasource of the same name. It will fail with exception complaining about existence of *.xml file. 


This is the same behaviour as described in 885136