Changes between Version 3 and Version 4 of LEGACY - CaTissueClientAPI

Timestamp:

11/26/10 10:40:50 (14 years ago)

Author:

jeff.lusted

Comment:

--

LEGACY - CaTissueClientAPI

@@ -5 +5 @@
 The client API allows you to use caTissue's domain objects (like Participant or Specimen) within another application (the client). All of the domain objects are serializable Java classes. The modus operandi is for the client to create or retrieve one of these and pass back the object to caTissue. The object gets serialized over the network for this to work.
 
-Here is some pseudo code what a client must do to register a new participant, with comments:
+Here is some pseudo code of what a client must do to register a new participant, with comments:
 
   1. Locate caTissue application service.
   1. Start a session within caTissue. This is just like any other interaction. There is the possibility of time out with inactivity.
-  1. Use application service to retrieve local copy of !CollectionProtocol.
-  1. Create local copy of Participant and initialize according to the !CollectionProtocol requirements. This is quite an involved process requiring knowledge of the caTissue business model.
-  1. Use application service to pass Participant to caTissue. After this action, the Participant exists in the database. 
+  1. Use application service to retrieve a local copy of the !CollectionProtocol.
+  1. Create a local copy of the Participant and initialize it according to the !CollectionProtocol requirements. This is quite an involved process requiring knowledge of the caTissue business model.
+  1. Use the application service to pass the Participant back to caTissue. After this action, the Participant exists in the database.