Changes between Version 9 and Version 10 of LEGACY - CaTissueClientAPI
- Timestamp:
- 11/26/10 12:34:44 (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
LEGACY - CaTissueClientAPI
v9 v10 31 31 === Transactions === 32 32 This is partly an extension of the above points on Domain Objects.[[BR]] 33 Normally, a business action within an application is defined by one or more transactions. I cannot see a clear transaction boundary yet in the API. 33 Normally, a business action within an application is defined by one or more transactions. I cannot see a clear transaction boundary yet in the API. The following is a tidied up code example of updating a Specimen Collection Group. The client has already done steps 1, 2, and 3. What you see below covers steps 4 and 5. 34 34 35 35 {{{ … … 63 63 } 64 64 }}} 65 66 Note that it is not entirely clear where a transaction begins or ends. There is no declaration of transaction boundaries visible. The application service object supports a number of methods, amongst which are CRUD like functions: methods whose signatures begin "create", "get", "query", "register", "remove", "search" or "update". I would suspect each of these might be seen from the caTissue end as a separate transaction. If that is the case, the example above covers a number of separate transactions.
