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
Label
Projects
Milestones
Assignee
Sort
Issues list
Health Indicator for Event Processors
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.
#2138
opened Mar 17, 2022 by
smcvb
Allow parameterized 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.
ResponseType
Priority 3: Could
#1537
opened Oct 13, 2020 by
jnfeinstein
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
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
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
Support SpEL on an 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.
@ProcessingGroup
annotation equivalent
Priority 4: Would
#1266
opened Nov 6, 2019 by
jangalinski
Graceful recovery from broken connections - MultiStreamableMessageSource
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.
#1327
opened Jan 22, 2020 by
smcvb
Improve support for hierarchical Spring application contexts
Epic
#1341
opened Feb 11, 2020 by
OLibutzki
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
Interceptor list Spring auto configuration
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.
#1422
opened Apr 24, 2020 by
smcvb
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
QueryUpdateEmitter should return a number of affected queries
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.
#1470
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
Inconsistency in AggregateTestFixture with constructor command handlers
Type: Bug
Use to signal issues that describe a bug within the system.
#3020
opened May 6, 2024 by
CodeDrivenMitch
Improved API for Aggregate State Transitions
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.
#1415
opened Apr 21, 2020 by
vab2048
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
AggregateLifecycle.createNew does not return Entity ID in CommandResultMessage
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.
#2059
opened Dec 22, 2021 by
jasperfect
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
Distinct 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.
Repository
beans based on configured Aggregate type
Priority 4: Would
#1688
opened Jan 22, 2021 by
gsteen
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
Return position after Append Events
Priority 1: Must
Highest priority. A release cannot be made if this issue isn’t resolved.
Type: Feature
Use to signal an issue is completely new to the project.
#1740
opened Mar 22, 2021 by
smcvb
Reject or warn about wrong usage of 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.
@EventHandler
and @EventSourcedHandler
annotations
Priority 4: Would
#1755
opened Apr 13, 2021 by
azzazzel
Rethink SnapshotFilter usage
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.
#1769
opened Apr 26, 2021 by
smcvb
Use PostgresTokenTableFactory when using H2 in PostgresSQL mode
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.
#1891
opened Jul 20, 2021 by
mikelhamer
ProTip!
Adding no:label will show everything without a label.