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

Support Kafka as EventBus Priority 3: Could Low priority. Issues that are nice to have but have a straightforward workaround. Status: Resolved Use to signal that work on this issue is done. Type: Feature Use to signal an issue is completely new to the project.
#375 by jangalinski was closed May 31, 2018 Release 3.3
@abuijze @nklmish
16 👍 10
Upgrade to Spring 6 and Spring Boot 3 Priority 1: Must Highest priority. A release cannot be made if this issue isn’t resolved. Status: Resolved Use to signal that work on this issue is done. Type: Dependency Upgrade Use to signal an issue that adjusts the project’s dependencies. Typically used by dependabot only.
#2430 by smcvb was closed Jan 20, 2023 Release 4.7.0
1
@gklijs
4 👍 9
Signal when all Handlers have been registered in Spring environment Priority 3: Could Low priority. Issues that are nice to have but have a straightforward workaround. Status: Resolved Use to signal that work on this issue is done. Type: Feature Use to signal an issue is completely new to the project.
#880 by smcvb was closed Apr 25, 2022 Release 4.6.0
2
@smcvb
1 👍 8
Provide fluent API to define Aggregate structure Status: Won't Fix Use to signal that the issue is acknowledged, but it’s decided that the work will not be performed. Type: Enhancement Use to signal an issue enhances an already existing feature of the project.
#526 by abuijze was closed Aug 6, 2019
@abuijze
3 👍 7
Support parallel processing in TrackingEventProcessor Priority 1: Must Highest priority. A release cannot be made if this issue isn’t resolved. Status: Resolved Use to signal that work on this issue is done. Type: Feature Use to signal an issue is completely new to the project.
#221 by abuijze was closed Oct 24, 2017 Release 3.1
@abuijze
4 👍 7
Query Repository for presence of Aggregate Identifier Priority 3: Could Low priority. Issues that are nice to have but have a straightforward workaround. Status: Duplicate Use to signal this issue is a duplicate of another. Please refer to the other issue. Status: Obsolete Use to signal this issue is no longer necessary. Type: Feature Use to signal an issue is completely new to the project.
#653 by smcvb was closed Dec 9, 2019
@smcvb
2 👍 6
Support Flux<...> as QueryHandler return type Priority 1: Must Highest priority. A release cannot be made if this issue isn’t resolved. Status: Duplicate Use to signal this issue is a duplicate of another. Please refer to the other issue. Status: Resolved Use to signal that work on this issue is done. Type: Feature Use to signal an issue is completely new to the project.
#1002 by raphael-jungers was closed Sep 27, 2022 Release 4.6.0
@schananas @smcvb @m1l4n54v1c
8 👍 6
Dead-Letter Queue for Event Processors Priority 1: Must Highest priority. A release cannot be made if this issue isn’t resolved. Status: Resolved Use to signal that work on this issue is done. Type: Feature Use to signal an issue is completely new to the project.
#2021 by smcvb was closed Sep 7, 2022 Release 4.6.0
1
@CodeDrivenMitch @smcvb
4 👍 5
Provide support for graceful startup / shutdown Priority 1: Must Highest priority. A release cannot be made if this issue isn’t resolved. Status: Resolved Use to signal that work on this issue is done. Type: Feature Use to signal an issue is completely new to the project.
#891 by abuijze was closed Feb 19, 2020 Release 4.3
1
@smcvb @m1l4n54v1c
3 👍 5
Enable auto-configuration of GenericJpaRepository with axon-spring Priority 2: Should High priority. Ideally, these issues are part of the release they’re assigned to. Status: Resolved Use to signal that work on this issue is done. Type: Feature Use to signal an issue is completely new to the project.
#234 by mark-verebelyi was closed Nov 13, 2017 Release 3.1
@abuijze
2 👍 4
Allow Commands to create-or-update an Aggegate Priority 2: Should High priority. Ideally, these issues are part of the release they’re assigned to. Status: Resolved Use to signal that work on this issue is done. Type: Feature Use to signal an issue is completely new to the project.
#667 by abuijze was closed Dec 13, 2019 Release 4.3
@MGathier
4 👍 4
Simplify configuration of TrackingSagaManager in Axon-Spring module Priority 2: Should High priority. Ideally, these issues are part of the release they’re assigned to. Status: Resolved Use to signal that work on this issue is done. Type: Feature Use to signal an issue is completely new to the project.
#230 by abuijze was closed Nov 6, 2017 Release 3.1
@abuijze
1 👍 4
Provide API to trigger replays Priority 1: Must Highest priority. A release cannot be made if this issue isn’t resolved. Status: Resolved Use to signal that work on this issue is done. Type: Feature Use to signal an issue is completely new to the project.
#441 by abuijze was closed Feb 11, 2018 Release 3.2
@abuijze
3 👍 4
Bug: ResultValidatorImpl expectEvents for EventMessage... will always reportWrongEvent Priority 3: Could Low priority. Issues that are nice to have but have a straightforward workaround. Status: Resolved Use to signal that work on this issue is done. Type: Bug Use to signal issues that describe a bug within the system.
#725 by NRBPerdijk was closed Aug 23, 2018 Release 3.3.6
@NRBPerdijk
4 👍 4
EmbeddedEventStore Thread Factory Priority 2: Should High priority. Ideally, these issues are part of the release they’re assigned to. Status: Resolved Use to signal that work on this issue is done. Type: Enhancement Use to signal an issue enhances an already existing feature of the project.
#735 by tgippi was closed Sep 25, 2018 Release 3.4
1
@tgippi
10 👍 3
End Saga when Deadline expires Priority 3: Could Low priority. Issues that are nice to have but have a straightforward workaround. Status: Resolved Use to signal that work on this issue is done. Type: Feature Use to signal an issue is completely new to the project.
#1469 by m1l4n54v1c was closed Jan 18, 2021 Release 4.5
1
@smcvb
👍 3
Automatic @Revision-based SnapshotFilter Priority 3: Could Low priority. Issues that are nice to have but have a straightforward workaround. Status: Resolved Use to signal that work on this issue is done. Type: Feature Use to signal an issue is completely new to the project.
#1588 by smcvb was closed Jan 11, 2021 Release 4.5
1
@smcvb
👍 3
Re-use Jackson ObjectMapper bean when auto-configuring a JacksonSerializer Priority 2: Should High priority. Ideally, these issues are part of the release they’re assigned to. Status: Resolved Use to signal that work on this issue is done. Type: Enhancement Use to signal an issue enhances an already existing feature of the project.
#671 by fransvanbuul was closed Sep 25, 2018 Release 3.4
1
@smcvb
👍 3
Gaps list huge in Tracking Event Processor Status: Information Required Use to signal this issue is waiting for information to be provided in the issue's description. Status: Resolved Use to signal that work on this issue is done. Type: Bug Use to signal issues that describe a bug within the system. Type: Question Use to signal the issue is a question of how the project works and thus does not require development
#2728 by Wmaarts was closed Jun 5, 2023
@smcvb @Wmaarts
5 👍 3
Support for OpenZipkin Status: Obsolete Use to signal this issue is no longer necessary. Type: Feature Use to signal an issue is completely new to the project.
#608 by nklmish was closed Aug 6, 2019
@abuijze
2 👍 3
Potential conflict between Kafka partitioning and Axon segmentation Priority 1: Must Highest priority. A release cannot be made if this issue isn’t resolved. Type: Bug Use to signal issues that describe a bug within the system.
#762 by altroy75 was closed Oct 19, 2018
@nklmish
7 👍 3
@TargetAggregateVersion @AggregateVersion documentation / examples ? Status: Won't Fix Use to signal that the issue is acknowledged, but it’s decided that the work will not be performed. Type: Question Use to signal the issue is a question of how the project works and thus does not require development
#721 by benneq was closed Aug 20, 2018
3 👍 3
Improved Deadline API Priority 1: Must Highest priority. A release cannot be made if this issue isn’t resolved. Status: Resolved Use to signal that work on this issue is done. Type: Feature Use to signal an issue is completely new to the project.
#220 by abuijze was closed Jul 3, 2018 Release 3.3
1
@smcvb @m1l4n54v1c
1 👍 3
Allow an Aggregate to easily access it's own version Priority 4: Would Lowest priority. Would-be-nice to include issues when time allows it. Status: Resolved Use to signal that work on this issue is done. Type: Feature Use to signal an issue is completely new to the project.
#543 by abuijze was closed Apr 10, 2018 Release 3.3
@m1l4n54v1c
👍 2
Cookbook recipe for configuration
#506 by sahina was closed Feb 14, 2018
2 👍 2
ProTip! Exclude everything labeled bug with -label:bug.