-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dataspace Discovery Service handle multiple EDC-Urls received for BPN #214
Comments
see EndpointDataForConnectorsService.findEndpointDataForConnectors which returns List<CompletableFuture> now instead of EndpointDataReference
As discussed in the daily on Jan, 30 the following remaining scenarios will be implemented in #395:
|
Analysis why this story takes much longer than estimated:
|
test on DEV with:
job run against deployed main:
same job run against deployed branch (PR-711):
|
there were some fixes in main, therefore it is required to merge and test again |
main:
branch: Duration: 0 days, 0 hours, 2 minutes, 0 seconds
Result looks identical besides other order. No significat performance change. In this single case it is 17 sec faster now. But if we want a performance measurement we would need some load test. |
…plantuml because currently we don't support mermaid there
switch log.debug to info because debug does not seem to get logged and add special marker "#214@" to filter the logs for debugging the story
This commit corrects the glossary sort order and adds some missing definitions, explanations and links.
…ug infos Moved logging from helper class to business class because this way the log entry shows the business class and not the helper class.
As User
I want that all EDCUrls are used for sending notifications and results are handled in a correct manner
so that all valid EDCUrls were used for ess investigation and provide correct results
Hints / Details
Outcome / Acceptance Criteria
Outcome
Acceptance Criteria
Out of Scope
The text was updated successfully, but these errors were encountered: