Do stack really need to dispatch ENTRY_STATE_CHANGE event for RecordingRequest delete() operation ??
When recRequest.delete() is called, it internally stops the recording and then it deletes the recording. During the process, after stop() the stack dispatches ENTRY_STATE_CHANGE (for INCOMPLETE_STATE) event followed by ENTRY_DELETED.
MY QUESTION : Do the stack need to really dispatch ENTRY_STATE_CHANGE for INCOMPLETE_STATE when it is finally going to delete the recording giving "ENTRY_DELETED"??
Issue : If i want to track whether the delete is succesful or not . I am looking for ENTRY_DELETED but before ENTRY_DELETED the stack dispatches ENTRY_STATE_CHANGE (for INCOMPLETE_STATE), my code is handling ENTRY_STATE_CHANGE separately where i query the recordingState by calling recordingChangedEvent.getRecordingRequest().getState(); But by the time i query the state for ENTRY_STATE_CHANGE event, the stack deletes the recording moves the state to DESTROYED state which results in IllegalStateException even though the ENTRY_DELETED event is not dispatched by the stack.
I feel it would be better if the user is given only ENTRTY_DELETED callback only after delete opertaion. Let the recording get stopped but notifying the appication for INCOMPLETE_STATE is not worth in delete case where tha main intention is to receive ENTRY_DELETED.
Please let me know your inputs on this.