Currently the repository needs to be restarted after a connector is changed/added/removed. So with the current behavior, the bug is the fact that Wildfly doesn't tell you it needs to be restarted after you add the connector.
However, in theory, you shouldn't have to restart the entire repository and it should be possible to just refresh the connectors. This is a bit more convoluted code-wise, but you could log an enhancement request for this.
Is there a way to only restart the repository? So far I only found a reload on the root from Wildfly what basically restarts everything.
For both the subsystem as for repository it shows me the following list of operations:
IIRC these are the default Wildfly Management API operations. To answer your question, no, there is no way to just restart a repository via the WF Mgmt console, you have to :reload the entire server.
The alternative is to write your own custom code which restarts the repository (using the ModeShape API) but that would be outside the management API.
Could you give me some pointers on where to look in the Modeshape API to restart the repository?
Thinking about this, in the context of Wildfly restarting a ModeShape repository via the API (essentially using the ModeShapeEngine class from the modeshape-core module) will not work. This is because in Wildfly there are other abstractions (mainly Wildfly Services) which need to be started and stopped for repositories, binary stores, connectors etc to work. Simply put, everything around restarting is much more complicated in Wildfly.
So I don't see a way to work around this atm. In the case of connectors we'd have to enhance the code to support the feature of "hot-swapping" connectors in Wildfly.