
9 Nov
2006
9 Nov
'06
6:34 p.m.
When I try to destroy a Finished job through the Platform endpoint, it always returns the following error: java.lang.Exception: Unable to destroy job: Activity identified by EPR has finished already Is this because the service doesn't have any per-job state? Are these semantics acceptable. The BES spec doesn't really say anything about the semantics of calling this operation after the job status is Finished. I treats it more like a cancel operation. The description of the Finished state also doesn't say anything about what this means with respect to a job's state. Anyway, I'm not trying to pick on Platform for doing it this way, but I think it's an interesting question that should be addressed at some point. Peter