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

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 updated Apr 3, 2023
HandlerDefinitions and HandlerEnhancerDefinitions are shared between multiple Spring Application Contexts 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.
#2590 opened Feb 6, 2023 by nils-christian updated Feb 13, 2023
@smcvb
7
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 updated Feb 8, 2023
5
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 updated Oct 27, 2022
3
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 updated Oct 10, 2022
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 updated Oct 3, 2022
Builder pattern improvements 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.
#902 opened Nov 20, 2018 by m1l4n54v1c updated Oct 3, 2022
2
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 updated Oct 3, 2022
Implement and use Matcher#describeMismatch throughout axon-test module 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.
#2400 opened Sep 27, 2022 by fernanfs updated Oct 1, 2022
@fernanfs
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 updated Sep 1, 2022
6
Distributed Query Bus 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.
#613 opened Jun 5, 2018 by smcvb updated Jul 21, 2022
@smcvb
13
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 updated Jul 12, 2022
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 updated May 25, 2022
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 updated May 2, 2022
5
Enhance JdbcSagaStore with ability to specify the content type for the serialized saga. Ideal for Contribution 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.
#2214 opened Apr 29, 2022 by vab2048 updated May 2, 2022
1
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
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
7
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
@OLibutzki
7
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
2
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
3
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
13
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
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
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
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
6
ProTip! Mix and match filters to narrow down what you’re looking for.