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.

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

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

Issues list

Cache improvements Epic
#641 opened Jul 3, 2018 by m1l4n54v1c updated Oct 17, 2018
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
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
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
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
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
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
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
Improve support for hierarchical Spring application contexts Epic
#1341 opened Feb 11, 2020 by OLibutzki updated Feb 11, 2020
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
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
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
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
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
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
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 updated Dec 28, 2020
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 updated Jan 4, 2021
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 updated Jan 11, 2021
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 updated May 10, 2021
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 updated Jul 2, 2021
Allow asynchronous code in Sagas Priority 1: Must Highest priority. A release cannot be made if this issue isn’t resolved. Status: On Hold Use to signal that work on this issue is paused. The description should clarify why. Type: Feature Use to signal an issue is completely new to the project.
#1860 opened Jul 2, 2021 by cjdxhjj updated Jul 5, 2021
The RetryScheduler on the query bus/gateway 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.
#1692 opened Jan 29, 2021 by idugalic updated Dec 24, 2021
Starting a Saga conditionally 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.
#1900 opened Jul 26, 2021 by OLibutzki updated Mar 3, 2022
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 updated Mar 7, 2022
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 updated Mar 24, 2022
ProTip! Follow long discussions with comments:>50.