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
7 Open 6 Closed
7 Open 6 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

InfraConfiguration.springAxonConfigurer ignores ConfigurerModule.order() 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.
#2845 by OLibutzki was closed Sep 25, 2023 Release 4.8.3
@abuijze
5
ObjectMapper cannot be resolved from Spring Parent Context 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.
#2628 by OLibutzki was closed Mar 3, 2023 Release 4.8.0
1
@OLibutzki
5
PooledStreamingEventProcessor: Token is not updated if no matching event handler is present 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.
#1815 by OLibutzki was closed Jun 4, 2021 Release 4.5.2
@abuijze @smcvb
5
Spring: Upcasters are not executed in the correct order 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: Bug Use to signal issues that describe a bug within the system.
#1810 by OLibutzki was closed Jun 4, 2021 Release 4.5.2
@smcvb
1
Inconsistent API naming - Builder: coordinatorExecutor vs workerExecutorService Ideal for Contribution 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.
#1784 by OLibutzki was closed May 10, 2021 Release 4.5.1
@smcvb
1
Spring: HierarchicalBeanFactory is not supported 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.
#1055 by OLibutzki was closed May 6, 2019 Release 4.2
@OLibutzki
3
ProTip! Exclude everything labeled bug with -label:bug.