SimpleScheduleToken prevents serialization of Saga #28

Closed
abuijze opened this Issue Feb 3, 2012 · 0 comments

Projects

None yet

1 participant

@abuijze
Member
abuijze commented Feb 3, 2012

When using the SimpleEventScheduler, it is not possible to store the sagas in the JpaSagaRepository (or any other persistent store). This is due to the SimpleScheduleToken, which contains a Future.

Instead, the Scheduler should keep a Map of ID to Future of all the tasks. The ID can be a randomly generated string, and is serializable. The future would allow the scheduler to cancel a schedule.

@abuijze abuijze was assigned Feb 3, 2012
@abuijze abuijze added a commit that referenced this issue Feb 4, 2012
@abuijze abuijze Ensured that the scheduletoken is serializable (#28)
The ScheduleToken now only contains a String, which references the
scheulded task.
66ca904
@abuijze abuijze added a commit that referenced this issue Feb 4, 2012
@abuijze abuijze Ensured that the scheduletoken is serializable (#28)
The ScheduleToken now only contains a String, which references the
scheulded task.
1888d5c
@abuijze abuijze closed this Feb 4, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment