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
91 Open 1,085 Closed
91 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

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
3
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
3
Logging Suggestion 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.
#1424 opened Apr 28, 2020 by Sam-Kruglov
@smcvb
4
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
1
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
@smcvb
1
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
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
Allow parameterized ResponseType 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.
#1537 opened Oct 13, 2020 by jnfeinstein
5
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
1
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.
#1590 opened Nov 4, 2020 by smcvb Release 5.0.0
1
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 Repository beans based on configured Aggregate type 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.
#1688 opened Jan 22, 2021 by gsteen
3
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
2
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
4
Reject or warn about wrong usage of @EventHandler and @EventSourcedHandler annotations Priority 4: Would 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.
#1755 opened Apr 13, 2021 by azzazzel
6
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
2
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
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
3
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
@mikelhamer
6
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
@OLibutzki
7
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
5
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
8
ProTip! Mix and match filters to narrow down what you’re looking for.