Legacy Issue Number: 3556
Source: Japan Biological Informatics Consortium ( Martin Senger)
Life cycle of an AnalysisInstance. These objects have the back pointer
to their AnalysisServices. However, I can imagine the situation where
clients have AnalysisInstance objects stored somewhere and using them to
retrieve results of previously (even long ago) started and finished
This normal situation can become interesting if the server does not
provide that analysis any more. I feel that it would be still reasonable
to provide access to the old stored results.
But to allow it, our spec should mention this possibility - and allows
to have this back poiter empty. So the client will have access to their
data but with limited support from the server (for example the client
cannot get metadata because the corresponding analysis is simply dead).
Or we could say that the back poiner cannot remain empty but can return
NO_OBJ... or whatever sytem exception (in situations as described above)>.
Or, we'd have to change the readonly attribute to a method so that we
can add the exception.
Reported: BSA 1.0b1 — Tue, 11 Apr 2000 04:00 GMT
Disposition: Resolved — BSA 1.0
Accepted. Document the use of a CORBA system exception.
Updated: Fri, 6 Mar 2015 20:57 GMT
BSA — Life cycle of an AnalysisInstance
- Key: BSA-15
- OMG Task Force: Biomolecular Sequ. Analysis FTF