Skip to content

Conversation

@paullatzelsperger
Copy link
Member

What this PR changes/adds

This PR changes the ParticipantContextEventCoordinator such that ParticipantContext objects are always created in the inactive state.
Then, keys are generated/added and possibly activated, and only then is the ParticipantContext activated, causing the DID document to be published.

Why it does that

avoid multiple publications

Further notes

List other areas of code that have changed but are not necessarily linked to the main feature. This could be method
signature changes, package declarations, bugs that were encountered and were fixed inline, etc.

Linked Issue(s)

Closes #455

Please be sure to take a look at the contributing guidelines and our etiquette for pull requests.

@paullatzelsperger paullatzelsperger added the enhancement New feature or request label Sep 12, 2024
@paullatzelsperger paullatzelsperger force-pushed the feat/455_activate_participantcontext_explicitly branch from e191221 to 012e9d0 Compare September 12, 2024 12:21
@paullatzelsperger paullatzelsperger force-pushed the feat/455_activate_participantcontext_explicitly branch from 012e9d0 to ecec8b7 Compare September 12, 2024 12:25
@paullatzelsperger paullatzelsperger merged commit db0206e into eclipse-edc:main Sep 12, 2024
@paullatzelsperger paullatzelsperger deleted the feat/455_activate_participantcontext_explicitly branch September 12, 2024 12:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Activate ParticipantContext in an explicit step

2 participants