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
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
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
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
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
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
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
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
Implement Page and PageResponseType for QueryBus
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.
#486
opened Jan 29, 2018 by
smcvb
Automatic Aggregate Event Stream filtering
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.
#1589
opened Nov 4, 2020 by
smcvb
Aggregate Stream Refactoring Support
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.
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
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
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
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
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
Previous Next
ProTip!
What’s not been updated in a month: updated:<2024-04-20.