Fix createIntegrationConnector and update ComponentIdReport #8017
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.
Description
The createIntegrationConnector had its own implementation of createConnection. This was not working when the connection was a virtual connection so I switch it to use the generic handler version. This had different problems which are now fixed. Similar problem with createGovernanceService. The result is that there is one method for creating connectors in the generic handlers and it seems to work.
The BasicFilesMonitor integration connector has cataloguing folders with the file resource connector rather than the folder resource coonnector. This cause subsequent survey action services on the folder asset to fail.
The survey folder survey action service what having trouble ceating an external profile log file. This is resolved by using the Apache Commons FileUtils that is able to create intervening folders as part of a file create.
The ComponentIdReport now contains the data connectors, XTDB connector and survey action connectors.
Related Issue(s)
None
Testing
Release Notes & Documentation
These are just bug fixes.
Additional notes
None