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.

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

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

Issues list

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
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
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
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
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
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
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
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
PessimisticLockManager concurrency related NullPointerException 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.
#32 by nigelh2012 was closed Feb 17, 2012 Release 1.3
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
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
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
NPE in SagaAnnotationInspector when associationValue is null 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.
#38 by martintilma was closed Apr 13, 2012 Release 1.3
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
Update the file system event store 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.
#41 by fversnel was closed Jul 15, 2012 Release 2.0
Add generic types for aggregate identifier 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.
#42 by abuijze was closed Jun 22, 2012 Release 2.0
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
Add support for guaranteed event processing in asynchronous event handler Priority 4: Would Lowest priority. Would-be-nice to include issues when time allows it.
#2 by abuijze was closed Feb 8, 2012
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
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
ProTip! Adding no:label will show everything without a label.