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
67 Open 168 Closed
67 Open 168 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

Add support for Quarkus Priority 2: Should High priority. Ideally, these issues are part of the release they’re assigned to. Type: Feature Use to signal an issue is completely new to the project.
#1318 opened Jan 15, 2020 by tunovic
15
Alias/Business Name for an Event Priority 2: Should High priority. Ideally, these issues are part of the release they’re assigned to. Type: Enhancement Use to signal an issue enhances an already existing feature of the project.
#722 opened Aug 20, 2018 by m1l4n54v1c
13
Implement Page and PageResponseType for QueryBus Priority 4: Would Lowest priority. Would-be-nice to include issues when time allows it. Type: Feature Use to signal an issue is completely new to the project.
#486 opened Jan 29, 2018 by smcvb
12
AggregateLifecycle.createNew does not return Entity ID in CommandResultMessage Priority 4: Would Lowest priority. Would-be-nice to include issues when time allows it. Type: Feature Use to signal an issue is completely new to the project.
#2059 opened Dec 22, 2021 by jasperfect
8
Provide SQL for all Entities Ideal for Contribution Priority 4: Would Lowest priority. Would-be-nice to include issues when time allows it. Type: Feature Use to signal an issue is completely new to the project.
#1258 opened Nov 2, 2019 by jangalinski
8
Consistency gap in conjunction with state-stored aggregates Status: Under Discussion Use to signal that the issue in question is being discussed.
#1103 opened May 27, 2019 by OLibutzki
8
Projection Testing Priority 2: Should High priority. Ideally, these issues are part of the release they’re assigned to. Type: Feature Use to signal an issue is completely new to the project.
#729 opened Aug 23, 2018 by m1l4n54v1c
8
How to solve the issue of business validation inaccuracies caused by projection delays? Type: Enhancement Use to signal an issue enhances an already existing feature of the project.
#3017 opened Apr 29, 2024 by yyc6698
7
Fix some static analysis findings Ideal for Contribution Priority 4: Would Lowest priority. Would-be-nice to include issues when time allows it. Type: Enhancement Use to signal an issue enhances an already existing feature of the project.
#2594 opened Feb 8, 2023 by timtebeek
2 of 4 tasks
7
Support for query handlers with dynamic names Priority 4: Would Lowest priority. Would-be-nice to include issues when time allows it. Status: Under Discussion Use to signal that the issue in question is being discussed. Type: Feature Use to signal an issue is completely new to the project.
#2099 opened Feb 3, 2022 by nils-christian
7
High memory usage when large gaps appear in event store Priority 2: Should High priority. Ideally, these issues are part of the release they’re assigned to. Type: Enhancement Use to signal an issue enhances an already existing feature of the project.
#1241 opened Oct 9, 2019 by sgrimm
7
Reject or warn about wrong usage of @EventHandler and @EventSourcedHandler annotations Priority 4: Would Lowest priority. Would-be-nice to include issues when time allows it. Status: On Hold Use to signal that work on this issue is paused. The description should clarify why. Type: Enhancement Use to signal an issue enhances an already existing feature of the project.
#1755 opened Apr 13, 2021 by azzazzel
6
Improve support for a local event store Priority 2: Should High priority. Ideally, these issues are part of the release they’re assigned to. Type: Feature Use to signal an issue is completely new to the project.
#1342 opened Feb 11, 2020 by OLibutzki
6
Usage of Release Candidates Priority 4: Would Lowest priority. Would-be-nice to include issues when time allows it. Status: Under Discussion Use to signal that the issue in question is being discussed. Type: Feature Use to signal an issue is completely new to the project.
#2589 opened Feb 6, 2023 by OLibutzki
5
Testing command, event and aggregate (de)serialization Priority 3: Could Low priority. Issues that are nice to have but have a straightforward workaround. Type: Enhancement Use to signal an issue enhances an already existing feature of the project.
#1904 opened Aug 5, 2021 by maartenjanvangool
5
Allow parameterized ResponseType Priority 3: Could Low priority. Issues that are nice to have but have a straightforward workaround. Status: Under Discussion Use to signal that the issue in question is being discussed. Type: Enhancement Use to signal an issue enhances an already existing feature of the project.
#1537 opened Oct 13, 2020 by jnfeinstein
5
Contract Testing Priority 4: Would Lowest priority. Would-be-nice to include issues when time allows it. Type: Feature Use to signal an issue is completely new to the project.
#2990 opened Feb 28, 2024 by meierw
4
Table partitioning for event table Ideal for Contribution Priority 4: Would Lowest priority. Would-be-nice to include issues when time allows it. Type: Feature Use to signal an issue is completely new to the project.
#2979 opened Feb 14, 2024 by williancolognesitrimble
4
Support for Virtual Threads - JDK21 Priority 1: Must Highest priority. A release cannot be made if this issue isn’t resolved. Type: Enhancement Use to signal an issue enhances an already existing feature of the project.
#2710 opened May 14, 2023 by mjagus
4
AggregateTestFixture does not validate deadlines set in the past Priority 3: Could Low priority. Issues that are nice to have but have a straightforward workaround. Type: Enhancement Use to signal an issue enhances an already existing feature of the project.
#2460 opened Oct 27, 2022 by CodeDrivenMitch
4
Return position after Append Events Priority 1: Must Highest priority. A release cannot be made if this issue isn’t resolved. Type: Feature Use to signal an issue is completely new to the project.
#1740 opened Mar 22, 2021 by smcvb
4
Allow registration of Upcasters on all components that do serialization of messages Priority 2: Should High priority. Ideally, these issues are part of the release they’re assigned to. Type: Feature Use to signal an issue is completely new to the project.
#746 opened Sep 3, 2018 by abuijze
4
EventProcessingConfigurer should expose registered configurations Ideal for Contribution Priority 4: Would Lowest priority. Would-be-nice to include issues when time allows it. Type: Enhancement Use to signal an issue enhances an already existing feature of the project.
#2457 opened Oct 27, 2022 by nils-christian
3
Enable tracing in DisruptorCommandBus with SpanFactory Priority 3: Could Low priority. Issues that are nice to have but have a straightforward workaround. Type: Feature Use to signal an issue is completely new to the project.
#2402 opened Sep 27, 2022 by smcvb
3
Add the abilty to fail on unresolved deadline handlers Priority 3: Could Low priority. Issues that are nice to have but have a straightforward workaround. Type: Enhancement Use to signal an issue enhances an already existing feature of the project.
#2334 opened Aug 19, 2022 by YvonneCeelie
3
ProTip! Updated in the last three days: updated:>2024-05-09.