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
13 Open 1,127 Closed
13 Open 1,127 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

[#394] Introduce Context Aware Upcasters 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: Feature Use to signal an issue is completely new to the project.
#398 by smcvb was closed Oct 28, 2017 Loading… Release 3.1
@smcvb
1
Add Sequence Name to @GeneratedValue() annotation
#238 by smcvb was closed Jan 19, 2017 Loading…
@abuijze @smcvb
1
Unable to use JacksonSerializer with DistributedCommandBus 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.
#239 by alexey-krylov was closed Jan 19, 2017 Release 3.0.1
@smcvb
6
Distinguish between Serializer for Events and general purpose serializer 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: Feature Use to signal an issue is completely new to the project.
#270 by abuijze was closed Nov 27, 2017 Release 3.1
@smcvb
2
Add Auto Configuration for Spring Cloud Connector set up 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: Feature Use to signal an issue is completely new to the project.
#305 by smcvb was closed Apr 10, 2017 Release 3.0.3
@smcvb
Allow more fine grained configuration control in @Aggregate annotation 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: Feature Use to signal an issue is completely new to the project.
#337 by abuijze was closed Nov 22, 2017 Release 3.1
@smcvb
SpringCloudCommandRouter fails to update membership metadata 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.
#343 by sofiaguyang was closed Nov 13, 2017 Release 3.1
@smcvb
6
Add additional CommandFilter look up mechanism to SpringCloudCommandRouter for added resilience 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.
#350 by smcvb was closed Nov 8, 2017 Release 3.1
@smcvb
1
Add an abstract EventMultiUpcaster 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: Feature Use to signal an issue is completely new to the project.
#376 by smcvb was closed Jul 24, 2017 Release 3.0.6
@smcvb
[#376] Add an abstract EventMultiUpcaster 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: Feature Use to signal an issue is completely new to the project.
#377 by smcvb was merged Jul 24, 2017 Loading… Release 3.0.6
@smcvb
@EventSourcingHandlers on @AggregateMembers should only receive events matching the @EntityId 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: Feature Use to signal an issue is completely new to the project.
#388 by tbvh was closed Nov 24, 2017 Release 3.1
@smcvb
3
Introduce context aware Upcaster interfaces 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: Feature Use to signal an issue is completely new to the project.
#394 by smcvb was closed Nov 13, 2017 Release 3.1
@smcvb
1
Improved Deadline API 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: Feature Use to signal an issue is completely new to the project.
#220 by abuijze was closed Jul 3, 2018 Release 3.3
1
@smcvb @m1l4n54v1c
1
Enhance AggregateTestFixture and ResultValidator to be able to assert expected commands Type: Question Use to signal the issue is a question of how the project works and thus does not require development
#397 by sofiaguyang was closed Jul 6, 2018
@smcvb
5
[#350] Add additional Command Routing Information look up mechanism to SpringCloudCommandRouter to cover more Spring Cloud implementations 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.
#414 by smcvb was merged Nov 8, 2017 Loading… Release 3.1
@smcvb
22
[#388] Introduce specific Event Routing capabilities for the Entities within an Aggregate 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: Feature Use to signal an issue is completely new to the project.
#436 by smcvb was merged Nov 24, 2017 Loading… Release 3.1
@smcvb
19
[#270] Distinguish between Serializer for Events and general purpose serializer 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: Feature Use to signal an issue is completely new to the project.
#444 by smcvb was merged Nov 27, 2017 Loading… Release 3.1
@smcvb
1
Error on updateMemberships with non axon apps on service discovery 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.
#458 by loutente was closed Dec 13, 2017 Release 3.1.1
@smcvb
2
Query API makes it hard to declare collections as return type 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: Enhancement Use to signal an issue enhances an already existing feature of the project.
#463 by abuijze was closed Mar 5, 2018 Release 3.2
@smcvb
1
ServiceInstance Black listing in SpringCloudCommandRouter has no effect 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.
#467 by smcvb was closed Jan 3, 2018 Release 3.1.2
@smcvb
1
Add Jackson de-/serialize annotations to MessageRoutingInformation 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.
#475 by smcvb was closed Jan 11, 2018 Release 3.1.2
@smcvb
1
"Aggregate identifier must be non-null" error with spring-boot-devtools on the classpath Priority 2: Should High priority. Ideally, these issues are part of the release they’re assigned to. Status: Obsolete Use to signal this issue is no longer necessary. Type: Enhancement Use to signal an issue enhances an already existing feature of the project.
#478 by donovanmuller was closed Mar 23, 2020 Release 4.4
@smcvb
2
Adjust SagaLifecycle.associateWith to allow an Object as association value Priority 4: Would Lowest priority. Would-be-nice to include issues when time allows it. Status: Won't Fix Use to signal that the issue is acknowledged, but it’s decided that the work will not be performed. Type: Enhancement Use to signal an issue enhances an already existing feature of the project.
#481 by smcvb was closed Feb 6, 2018 Release 3.2
@smcvb
2
Inconsistency between CommandValidator and EventValidator 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.
#483 by sofiaguyang was closed May 29, 2019 Release 4.2
@smcvb
Bump the github-dependencies group with 2 updates
Priority 1: Must Highest priority. A release cannot be made if this issue isn’t resolved. Type: Dependency Upgrade Use to signal an issue that adjusts the project’s dependencies. Typically used by dependabot only.
#3014 by dependabot bot was merged Apr 22, 2024 Loading… Release 4.10.0
@smcvb
4
ProTip! Add no:assignee to see everything that’s not assigned.