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

Need code examples 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.
#15 by abuijze was closed Apr 8, 2012 Release 2.0
@abuijze
Add suggestions about architecture design choices with Axon
#3 by abuijze was closed Dec 30, 2016
Automated creation of wiring diagram.
#4 by abuijze was closed Dec 30, 2016
Support for aggregate without extending an Axon class
#5 by abuijze was closed Dec 30, 2016
7
Remoting CommandBus 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.
#6 by abuijze was closed Dec 30, 2016 Release 2.0
@abuijze
Create connector to remotely connect event busses 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. Type: Feature Use to signal an issue is completely new to the project.
#7 by abuijze was closed Dec 30, 2016 Release 2.0
@abuijze
6
Distributed command bus 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.
#8 by abuijze was closed Apr 8, 2012 Release 2.0
@abuijze
1
Improve processing performance for sagas Type: Enhancement Use to signal an issue enhances an already existing feature of the project.
#9 by abuijze was closed Apr 8, 2012
@abuijze
Implement a disruptor-based high-performance commandbus 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: Enhancement Use to signal an issue enhances an already existing feature of the project.
#10 by abuijze was closed May 8, 2012 Release 2.0
@abuijze
4
Repository doesn't throw exception when storing wrong type of aggregate 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.
#11 by abuijze was closed Dec 30, 2016 Release 2.0
@abuijze
2
High performance snapshotter 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.
#12 by abuijze was closed Dec 30, 2016 Release 2.0
@abuijze
Respect ordering of ApplicationEvent and DomainEvents registration with a UnitOfWork 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.
#13 by abuijze was closed Apr 8, 2012 Release 2.0
@abuijze
1
Create 5 minute introduction to CQRS / Axon Priority 4: Would Lowest priority. Would-be-nice to include issues when time allows it.
#1 by abuijze was closed Dec 30, 2016
Enhance EventStoreManagement 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.
#14 by abuijze was closed Apr 8, 2012 Release 2.0
@abuijze
1
Generic test to verify that Aggregate state is only manipulated through event handlers 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: Enhancement Use to signal an issue enhances an already existing feature of the project.
#16 by abuijze was closed Feb 10, 2012 Release 2.0
@abuijze
1
Mongo MongoEventStoreBenchMark could be faster Priority 4: Would Lowest priority. Would-be-nice to include issues when time allows it.
#17 by abuijze was closed Dec 30, 2016
Improve Event API by extracting application-specific payload 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.
#18 by abuijze was closed Apr 8, 2012 Release 2.0
@abuijze
Allow configuration of persistence unit in JPA-specific components 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.
#19 by abuijze was closed Jan 2, 2012 Release 1.3
@abuijze
Improve Jpa (and FS) Event Stores so that only payload (and headers) need to be serialized 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: Enhancement Use to signal an issue enhances an already existing feature of the project.
#20 by abuijze was closed Apr 8, 2012 Release 2.0
@abuijze
Make message MetaData immutable 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.
#21 by abuijze was closed Feb 8, 2012 Release 2.0
@abuijze
Enhance Domain Model: allow any Object as AggregateIdentifier 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: Enhancement Use to signal an issue enhances an already existing feature of the project.
#22 by abuijze was closed Apr 8, 2012 Release 2.0
@abuijze
3
Create annotation based cluster selector 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.
#23 by abuijze was closed Jul 17, 2012 Release 2.0
@abuijze
1
Provide infrastructure for replaying events 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.
#25 by abuijze was closed Dec 30, 2016 Release 2.0
@abuijze
CommandTemplate 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.
#26 by abuijze was closed Jan 2, 2012 Release 1.3
@abuijze
1
OpenTelemetry Issue - Span ended without all scopes! Status: Information Required Use to signal this issue is waiting for information to be provided in the issue's description. Type: Bug Use to signal issues that describe a bug within the system.
#3012 by gabrieldimech was closed May 3, 2024 Release 4.9.4
@abuijze @gklijs
3
ProTip! What’s not been updated in a month: updated:<2024-04-09.