ActivityLedger Needs to Recover if Posting Did Not Complete at Startup
Description
The user would like the activity ledger to recover if the application unexpectedly terminates during startup.
To address this issue, we're going to need to do a couple of things:
Create a new configuration object for the ActivityLedger with a single boolean value that indicated a re-posting of ActivityLedgers is required at startup
If this value is set to true, we should unconditionally remove/re-post all ledgers
Add a method to the ActivityLedgerService that returns the status of a given ActivityLedgerPosting job. This will involve using the monitor service to retrieve the status of the job.
If, on startup, the status for any of these jobs indicates failure, we need to remove/re-post the ActivityLedgers
__NOTE: This could be optimized to remove/re-post only ledgers for the failed job...but, for now, we're electing to just re-post all ledgers
The user would like the activity ledger to recover if the application unexpectedly terminates during startup.
To address this issue, we're going to need to do a couple of things:
Create a new configuration object for the ActivityLedger with a single boolean value that indicated a re-posting of ActivityLedgers is required at startup
If this value is set to true, we should unconditionally remove/re-post all ledgers
Add a method to the ActivityLedgerService that returns the status of a given ActivityLedgerPosting job. This will involve using the monitor service to retrieve the status of the job.
If, on startup, the status for any of these jobs indicates failure, we need to remove/re-post the ActivityLedgers
__NOTE: This could be optimized to remove/re-post only ledgers for the failed job...but, for now, we're electing to just re-post all ledgers