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

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
Automatic migration recipes to 4.7+ Ideal for Contribution 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.
#2596 by timtebeek was closed Feb 14, 2023 Release 4.7.2
Allow for custom parameters to be provided when triggering a reset 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.
#1390 by abuijze was closed Jun 24, 2020 Release 4.4
Pick up Aggregate Cache in (Spring Auto) Configuration Ideal for Contribution 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.
#1206 by quaso was closed Jan 2, 2020 Release 4.3
Tracking Event Processor OnStatustUpdate hook 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.
#1338 by schananas was closed Jul 27, 2020 Release 4.4
Prefer 'deregister' to 'unregister' 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: Enhancement Use to signal an issue enhances an already existing feature of the project.
#2456 by vab2048 was closed Oct 31, 2022 Release 4.6.2
Remoting CommandBus 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: Enhancement Use to signal an issue enhances an already existing feature of the project.
#6 by abuijze was closed Dec 30, 2016 Release 2.0
Distributed command bus 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.
#8 by abuijze was closed Apr 8, 2012 Release 2.0
Improve processing performance for sagas Type: Enhancement Use to signal an issue enhances an already existing feature of the project.
#9 by abuijze was closed Apr 8, 2012
Repository doesn't throw exception when storing wrong type of aggregate 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: Bug Use to signal issues that describe a bug within the system.
#11 by abuijze was closed Dec 30, 2016 Release 2.0
High performance snapshotter 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.
#12 by abuijze was closed Dec 30, 2016 Release 2.0
Respect ordering of ApplicationEvent and DomainEvents registration with a UnitOfWork 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: Enhancement Use to signal an issue enhances an already existing feature of the project.
#13 by abuijze was closed Apr 8, 2012 Release 2.0
OpenTelemetry Issue - Span ended without all scopes! Status: Information Required Use to signal this issue is waiting for information to be provided in the issue's description. Type: Bug Use to signal issues that describe a bug within the system.
#3012 by gabrieldimech was closed May 3, 2024 Release 4.9.4
Improve Event API by extracting application-specific payload 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: Enhancement Use to signal an issue enhances an already existing feature of the project.
#18 by abuijze was closed Apr 8, 2012 Release 2.0
Allow configuration of persistence unit in JPA-specific components 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.
#19 by abuijze was closed Jan 2, 2012 Release 1.3
Improve Jpa (and FS) Event Stores so that only payload (and headers) need to be serialized 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: Enhancement Use to signal an issue enhances an already existing feature of the project.
#20 by abuijze was closed Apr 8, 2012 Release 2.0
Make message MetaData immutable 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.
#21 by abuijze was closed Feb 8, 2012 Release 2.0
Create annotation based cluster selector 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.
#23 by abuijze was closed Jul 17, 2012 Release 2.0
Provide infrastructure for replaying events 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: Enhancement Use to signal an issue enhances an already existing feature of the project.
#25 by abuijze was closed Dec 30, 2016 Release 2.0
CommandTemplate 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.
#26 by abuijze was closed Jan 2, 2012 Release 1.3
Enhance EventStoreManagement 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.
#14 by abuijze was closed Apr 8, 2012 Release 2.0
ProTip! What’s not been updated in a month: updated:<2024-04-11.