There are two cases under delete.
Example for the first case:
CCB1 requests a createOp for Obj1 with a NO_DANGLING reference to the already
existing Obj2 and gets OK return.
CCB2 requests a delete of Obj2, but gets ERR_BUSY.
(This because CCB2 would interfere with CCB1 and since CCB1 was prior
So they are not exactly duplicates scenarios, but similar and possibly reverse
order of operation scnarios.
The intent is to descibe why you would get say ERR_BAD_OPERATION for a
ccbObjectCreate ot for a
ccbObjectDelete. The point here is that you get these errros for the
repsective
Anders,
I still have concerns about the documentation for error codes for CCB
Object Delete. The scenarios mentioned do not correspond to CCB Object
Delete but duplicate of the scenarios mentioned in CCB Object Create.
The only possibility of CCB Object Delete returning error is If an
object
osaf/services/saf/immsv/README.NO_DANGLING | 36 -
1 files changed, 29 insertions(+), 7 deletions(-)
diff --git a/osaf/services/saf/immsv/README.NO_DANGLING
b/osaf/services/saf/immsv/README.NO_DANGLING
--- a/osaf/services/saf/immsv/README.NO_DANGLING
+++
