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
Upcasters are not applied to DeadLetterQueue entries
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.
#2500
opened Nov 23, 2022 by
nils-christian
AggregateTestFixture does not validate deadlines set in the past
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.
#2460
opened Oct 27, 2022 by
CodeDrivenMitch
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
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
Allow for customization of queries in the 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.
JdbcTokenStore
Priority 3: Could
#2410
opened Sep 29, 2022 by
trimoq
Enable tracing in DisruptorCommandBus with SpanFactory
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.
#2402
opened Sep 27, 2022 by
smcvb
Implement and use 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.
Matcher#describeMismatch
throughout axon-test
module
Priority 3: Could
#2400
opened Sep 27, 2022 by
fernanfs
Aggregate Parameter Resolver
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.
#2399
opened Sep 27, 2022 by
smcvb
Add the abilty to fail on unresolved deadline handlers
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.
#2334
opened Aug 19, 2022 by
YvonneCeelie
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
Enhance 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.
JdbcSagaStore
with ability to specify the content type for the serialized saga.
Ideal for Contribution
Priority 3: Could
#2214
opened Apr 29, 2022 by
vab2048
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
Enhance 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.
ShutdownLatch#registerActivity
with a way to cancel the activity.
Priority 3: Could
#2147
opened Mar 21, 2022 by
m1l4n54v1c
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
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
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
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
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
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
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
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
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
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
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
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
ProTip!
Updated in the last three days: updated:>2024-05-06.