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
90 Open 1,085 Closed
90 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

Snapshot Warm-Up Service 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.
#1641 opened Dec 15, 2020 by smcvb updated Dec 15, 2020
Configuration Testing 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.
#1640 opened Dec 15, 2020 by smcvb updated Dec 15, 2020
Chaining Parameter Resolvers 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.
#1639 opened Dec 15, 2020 by smcvb updated Dec 15, 2020
State-Stored Aggregate: AggregateIdentifier has to be String 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.
#1062 opened Apr 18, 2019 by OLibutzki updated Oct 28, 2020
@abuijze @smcvb
10
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 updated Aug 11, 2020
8
Integration test facility to ensure and assert processed events 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.
#1426 opened Apr 30, 2020 by hatzlj updated Apr 30, 2020
1
Improve support for hierarchical Spring application contexts Epic
#1341 opened Feb 11, 2020 by OLibutzki updated Feb 11, 2020
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 updated Jan 27, 2020
7
Dynamic Configuration Changes 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.
#1276 opened Nov 26, 2019 by m1l4n54v1c updated Jan 16, 2020
Allow Map for ResponseType of a Query 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.
#1257 opened Nov 1, 2019 by Sam-Kruglov updated Nov 7, 2019
1
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 updated Oct 24, 2019
4
Ordering of event handler instance/type group selectors 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.
#1028 opened Mar 14, 2019 by m1l4n54v1c updated Aug 7, 2019
Introduce Federated/Hierarchical CommandBus 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.
#1092 opened May 15, 2019 by smcvb updated May 15, 2019
Custom Scopes 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.
#626 opened Jun 21, 2018 by m1l4n54v1c updated Oct 17, 2018
Cache improvements Epic
#641 opened Jul 3, 2018 by m1l4n54v1c updated Oct 17, 2018
ProTip! Mix and match filters to narrow down what you’re looking for.