MongoDBManager ignores webprotege.properties #65
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello,
When installing Webprotege, I used a MongoDB server that was not installed locally. I changed the settings in webprotege.properties and expected Webprotege to use the remote MongoDB server. However, I still saw Webprotege trying to connect locally.
After some exploring I found the MongoDBManager not getting the settings I had entered in the webprotege.properties file. To resolve that issue I made some changes in the MongoDBManager.
I have tested it, and it works for me on a remote and locally installed MongoDB server.
Kind regards,
Martijn Evers