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

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
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
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
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
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
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
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
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
Documentation Inconsistency: ctx with UUID not in AbstractAnnotatedAggregateRoot
#27 by rolandkofler was closed Feb 1, 2012
SimpleScheduleToken prevents serialization of Saga 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.
#28 by abuijze was closed Feb 4, 2012 Release 1.3
@abuijze
Race condition with garbage collector causing old Saga state to be produced 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.
#30 by abuijze was closed Feb 6, 2012 Release 1.3
@abuijze
Allow commands as "given" in test fixtures Type: Enhancement Use to signal an issue enhances an already existing feature of the project.
#31 by abuijze was closed Feb 10, 2012
Major documentation update 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.
#35 by abuijze was closed Dec 30, 2016 Release 2.0
@abuijze
MongoEventStore should store "commit" as Document 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.
#36 by abuijze was closed Dec 30, 2016 Release 2.0
@abuijze
NullPointerException when loading inexistent aggregate in GenericJpaRepository 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: Bug Use to signal issues that describe a bug within the system.
#37 by abuijze was closed Apr 10, 2012 Release 1.3
@abuijze
EventBus should allow more that one Event in the publish method 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.
#39 by abuijze was closed May 8, 2012 Release 2.0
GenericAggregateFactory should use default no-arg constructor 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.
#43 by abuijze was closed May 5, 2012 Release 2.0
@abuijze
EventScheduler should always create new Message instance at scheduled time 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.
#44 by abuijze was closed Jul 10, 2012 Release 2.0
@abuijze
Aggregate test fixture doesn't handle server generated identifiers very well 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.
#46 by abuijze was closed May 5, 2012 Release 2.0
@abuijze
PessimisticLockManager should detect deadlocks Type: Enhancement Use to signal an issue enhances an already existing feature of the project.
#47 by abuijze was closed Dec 30, 2016
ProTip! Type g p on any issue or pull request to go back to the pull request listing page.