Skip to content

[#3083] Configure application wide Clock#4591

Closed
jangalinski wants to merge 2 commits into
axon-5.1.xfrom
feature/3083/application-wide-clock
Closed

[#3083] Configure application wide Clock#4591
jangalinski wants to merge 2 commits into
axon-5.1.xfrom
feature/3083/application-wide-clock

Conversation

@jangalinski
Copy link
Copy Markdown
Collaborator

Introduced ClockUtils to replace GenericEventMessage.clock as the central keeper of current clock.

Hint:

  • most changes are related to the replacement of the static import
  • not yet included in ComponentRegistry

will fix #3083

- allows to get/set clock on a central util class without directly working with a static field
- adjusted all tests
- introduced timestamp-less constructor so only GenericEventMessage needs to know about the clock
- todo: also register in component registry
@jangalinski jangalinski self-assigned this May 19, 2026
@jangalinski jangalinski added this to the Release 5.1.1 milestone May 19, 2026
@hjohn
Copy link
Copy Markdown
Contributor

hjohn commented May 19, 2026

The ticket is targetted at 5.2.0, but this PR is targetted at Axon-5.1.x ?

@smcvb smcvb modified the milestones: Release 5.1.1, Release 5.2.0 May 20, 2026
@smcvb
Copy link
Copy Markdown
Contributor

smcvb commented May 20, 2026

The ticket is targetted at 5.2.0, but this PR is targetted at Axon-5.1.x ?

This should indeed be targeted towards main :-)

Comment thread common/src/main/java/org/axonframework/common/ClockUtils.java
@jangalinski
Copy link
Copy Markdown
Collaborator Author

Closing in favor of #4592 due to wrong target branch.

Copy link
Copy Markdown
Contributor

@smcvb smcvb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Two nits, otherwise this looks good to me. With the exception that it's targeted towards axon-5.1.x, while it's a change for main/5.2.0!

@jangalinski
Copy link
Copy Markdown
Collaborator Author

The nits where addressed in #4592

@smcvb smcvb removed this from the Release 5.2.0 milestone May 20, 2026
@smcvb smcvb added Type: Feature Use to signal an issue is completely new to the project. Priority 2: Should High priority. Ideally, these issues are part of the release they’re assigned to. Status: Obsolete Use to signal this issue is no longer necessary. labels May 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Priority 2: Should High priority. Ideally, these issues are part of the release they’re assigned to. Status: Obsolete Use to signal this issue is no longer necessary. Type: Feature Use to signal an issue is completely new to the project.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants