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

Make forwarding mode configurable for entire Aggregate instead of configuring for each AggregateMember 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.
#474 opened Jan 11, 2018 by marleinevankampen
TinyLFU-based caching policy 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.
#518 opened Feb 27, 2018 by ben-manes
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
Cache improvements Epic
#641 opened Jul 3, 2018 by m1l4n54v1c
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
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
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
Improve support for hierarchical Spring application contexts Epic
#1341 opened Feb 11, 2020 by OLibutzki
BufferingQueryUpdateEmitter 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.
#1471 opened Jul 22, 2020 by m1l4n54v1c
Provide a fluent API for assertions 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: Feature Use to signal an issue is completely new to the project.
#1476 opened Jul 27, 2020 by OLibutzki
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
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
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
EventSourcingRepository API to load an aggregate up to a specific 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.
#1661 opened Jan 4, 2021 by saratry
Unify annotation names 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.
#1781 opened May 7, 2021 by azzazzel
Enhance ShutdownLatch#registerActivity with a way to cancel the activity. 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.
#2147 opened Mar 21, 2022 by m1l4n54v1c
ExceptionHandler not invoked when QueryHandler returns a failed Future 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.
#2201 opened Apr 21, 2022 by YvonneCeelie
Allow EventHandlers be defined on methods coming from generic interfaces 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.
#2283 opened Jul 12, 2022 by trimoq
Aggregate Parameter Resolver 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.
#2399 opened Sep 27, 2022 by smcvb
Allow custom event validation implementations in the ResultValidator 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.
#2429 opened Oct 7, 2022 by fernanfs
Enable automatic processing dlq's from configuration 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.
#2672 opened Apr 3, 2023 by gklijs
Set initial token to head when all contained Event Handling Components of a Streaming Event Processor disallow replays 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.
#2760 opened Jun 20, 2023 by smcvb
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
1
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
1
Automatic Aggregate Event Stream filtering 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.
#1589 opened Nov 4, 2020 by smcvb
1
ProTip! Exclude everything labeled bug with -label:bug.