exist-db restxq trigger : Services deleted but still active

Question

I have issues with the RESTXQ implementation in exist-db. I think it might be the RestXQTrigger which is not working correctly.

The problem: I deleted (via the Dashboard) a collection including RESTXQ services inside several .xqm files. However, the services are not unregistered and are still available, even after restarting eXist.

Is there any way to force this unregistring, I mean other than recreate the previous collections/files and delete each .xqm files one by one (this way, the trigger seems to work) ?

Answer 1

You can stop the database, and manually remove the registry file $EXIST_HOME/webapp/WEBINF/data/restxq.registry