Skip to content

Issues: AxonFramework/AxonFramework

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.

Sign up for GitHub

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

Clear current search query, filters, and sorts
91 Open 1,085 Closed
91 Open 1,085 Closed
Author
Filter by author
Label
Filter by label
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Milestones
Filter by milestone
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Feature: Allow to read an aggregate in a specific (older) version Type: Feature Use to signal an issue is completely new to the project.
#627 by dhermanns was closed Jul 5, 2018
@abuijze
4 👍 2
Include an EventJobDataBinder that leverages an Axon Serializer Status: Duplicate Use to signal this issue is a duplicate of another. Please refer to the other issue.
#673 by fransvanbuul was closed Oct 5, 2018 Release 3.4
@smcvb
1 👍 2
Use ProjectReactor in Axon's messaging APIs Status: Won't Fix Use to signal that the issue is acknowledged, but it’s decided that the work will not be performed. Type: Enhancement Use to signal an issue enhances an already existing feature of the project.
#752 by abuijze was closed Oct 9, 2018
2 👍 2
Remove dynamic proxy for Command and Query handlers Priority 2: Should High priority. Ideally, these issues are part of the release they’re assigned to. Status: Resolved Use to signal that work on this issue is done. Type: Enhancement Use to signal an issue enhances an already existing feature of the project.
#744 by abuijze was closed Dec 21, 2023 Release 5.0.0
@abuijze @smcvb
1 👍 2
QuartzDeadlineManager does not recover from failures Priority 1: Must Highest priority. A release cannot be made if this issue isn’t resolved. Status: Resolved Use to signal that work on this issue is done. Type: Bug Use to signal issues that describe a bug within the system.
#2451 by CodeDrivenMitch was closed Nov 4, 2022 Release 4.6.2
@gklijs
1 👍 2
Default Tracking Token to head in case of Sagas Priority 4: Would Lowest priority. Would-be-nice to include issues when time allows it. Status: Resolved Use to signal that work on this issue is done. Type: Enhancement Use to signal an issue enhances an already existing feature of the project.
#1019 by smcvb was closed Jan 25, 2021 Release 4.5
1
@smcvb
7 👍 2
Distributed saga management Priority 2: Should High priority. Ideally, these issues are part of the release they’re assigned to. Status: Resolved Use to signal that work on this issue is done. Type: Feature Use to signal an issue is completely new to the project.
#331 by sofiaguyang was closed Oct 27, 2017 Release 3.1
@abuijze
8 👍 2
isCaughtUp() of TrackingEventProcessor always returns true Priority 1: Must Highest priority. A release cannot be made if this issue isn’t resolved. Status: Resolved Use to signal that work on this issue is done. Type: Bug Use to signal issues that describe a bug within the system.
#1505 by bastoker was closed Sep 22, 2020 Release 4.4.3
@bastoker @smcvb
11 👍 2
AggregateTestFixture behaves unexpectedly when attempting to create the same aggregate twice Type: Question Use to signal the issue is a question of how the project works and thus does not require development
#584 by jqno was closed May 4, 2018
@smcvb
4 👍 2
TrackingProcessor should trigger notification when reaching the head of the stream Priority 1: Must Highest priority. A release cannot be made if this issue isn’t resolved. Status: Resolved Use to signal that work on this issue is done. Type: Feature Use to signal an issue is completely new to the project.
#381 by abuijze was closed Mar 12, 2018 Release 3.2
@abuijze
6 👍 2
Allow disabling AxonServerAutoConfiguration via properties Ideal for Contribution Priority 3: Could Low priority. Issues that are nice to have but have a straightforward workaround. Status: Resolved Use to signal that work on this issue is done. Type: Feature Use to signal an issue is completely new to the project.
#1247 by jangalinski was closed Dec 30, 2019
@jangalinski
3 👍 2
Autoconfigure automatic load balancing Priority 2: Should High priority. Ideally, these issues are part of the release they’re assigned to. Status: Resolved Use to signal that work on this issue is done. Type: Feature Use to signal an issue is completely new to the project.
#2453 by CodeDrivenMitch was closed Jun 19, 2023 Release 4.8.0
1
@smcvb
3 👍 2
Allow an Aggregate to easily access it's own version Priority 4: Would Lowest priority. Would-be-nice to include issues when time allows it. Status: Resolved Use to signal that work on this issue is done. Type: Feature Use to signal an issue is completely new to the project.
#543 by abuijze was closed Apr 10, 2018 Release 3.3
@m1l4n54v1c
👍 2
JDK16 - axon-messaging own unit test fail on Priority 3: Could Low priority. Issues that are nice to have but have a straightforward workaround. Status: Resolved Use to signal that work on this issue is done. Type: Dependency Upgrade Use to signal an issue that adjusts the project’s dependencies. Typically used by dependabot only. Type: Enhancement Use to signal an issue enhances an already existing feature of the project.
#1826 by zcglisp was closed Jan 20, 2023 Release 4.7.0
@smcvb
18 👍 2
Make storage of "non domain events" optional Priority 2: Should High priority. Ideally, these issues are part of the release they’re assigned to. Status: Resolved Use to signal that work on this issue is done. Type: Feature Use to signal an issue is completely new to the project.
#235 by bilak was closed Nov 13, 2017 Release 3.1
@abuijze
👍 2
EventSourcingRepository should only handle DomainEvents for the type of the Repository Priority 2: Should High priority. Ideally, these issues are part of the release they’re assigned to. Status: Resolved Use to signal that work on this issue is done. Type: Enhancement Use to signal an issue enhances an already existing feature of the project.
#587 by abbierwolf was closed Jun 25, 2018 Release 3.3
1
@smcvb @abbierwolf
2 👍 2
Support defining Command Handler Interceptors in Command Model Entities Priority 2: Should High priority. Ideally, these issues are part of the release they’re assigned to. Status: Resolved Use to signal that work on this issue is done. Type: Feature Use to signal an issue is completely new to the project.
#558 by abuijze was closed Apr 18, 2018 Release 3.3
@m1l4n54v1c
👍 2
Cookbook recipe for configuration
#506 by sahina was closed Feb 14, 2018
2 👍 2
Add annotation NonNull/Nullable for better usage in kotlin (also java) Ideal for Contribution Priority 4: Would Lowest priority. Would-be-nice to include issues when time allows it. Status: Resolved Use to signal that work on this issue is done. Type: Enhancement Use to signal an issue enhances an already existing feature of the project.
#1280 by Blackdread was closed Mar 28, 2022 Release 4.6.0
1
@CodeDrivenMitch
5 👍 2
Spring: Place the Axon shutdown hook AFTER the WebServer ones Priority 3: Could Low priority. Issues that are nice to have but have a straightforward workaround. Status: Resolved Use to signal that work on this issue is done. Type: Enhancement Use to signal an issue enhances an already existing feature of the project.
#3007 by bystam was closed Apr 15, 2024 Release 4.10.0
@bystam
3 👍 2
Enable customization of gRPC channel to AxonServer through AxonServerConnectionManager Priority 3: Could Low priority. Issues that are nice to have but have a straightforward workaround. Status: Resolved Use to signal that work on this issue is done. Type: Enhancement Use to signal an issue enhances an already existing feature of the project.
#1504 by MGathier was closed Sep 22, 2020 Release 4.4.3
@MGathier
1 👍 2
Introduce Polymorphic Aggregate Snapshotting auto-configuration Priority 2: Should High priority. Ideally, these issues are part of the release they’re assigned to. Status: Resolved Use to signal that work on this issue is done. Type: Feature Use to signal an issue is completely new to the project.
#2689 by smcvb was closed Jun 16, 2023 Release 4.8.0
1
@smcvb
👍 2
Introduce a 'registerProjection()'/registerMessageHandler() configuration function Priority 3: Could Low priority. Issues that are nice to have but have a straightforward workaround. Status: Resolved Use to signal that work on this issue is done. Type: Feature Use to signal an issue is completely new to the project.
#720 by smcvb was closed Jul 13, 2020 Release 4.4
@smcvb
👍 1
Add defaultHandlerInterceptors to BuildEventProcessor() in EventProcessingConfiguration Priority 1: Must Highest priority. A release cannot be made if this issue isn’t resolved. Status: Resolved Use to signal that work on this issue is done. Type: Bug Use to signal issues that describe a bug within the system.
#723 by marleinevankampen was closed Sep 25, 2018 Release 3.3.6
@marleinevankampen
1 👍 1
Simplify configuration of Event Handling Priority 1: Must Highest priority. A release cannot be made if this issue isn’t resolved. Status: Resolved Use to signal that work on this issue is done. Type: Enhancement Use to signal an issue enhances an already existing feature of the project.
#740 by abuijze was closed Oct 17, 2018 Release 4.0
@m1l4n54v1c
1 👍 1
ProTip! Mix and match filters to narrow down what you’re looking for.