| | 3 | SoapLab wraps business logic, described in ACD files. Often, the business logic is implemented as command-line applications. This includes those in Emboss. To support async access, SoapLab implements [http://www.omg.org/technology/documents/formal/lsae.htm lsae]. The implementation of this is documented at the [http://soaplab.sourceforge.net/soaplab2/API/index.html soaplab2 API], and in particular, the [http://soaplab.sourceforge.net/soaplab2/API/org/soaplab/share/Analysis.html Analysis] class. |
| | 4 | |
| | 5 | Asynchronous invocation is required by SoapLab as the underlying buisness logic may be long-running, and timeouts may occur in any layer of the transport between client and server. |
| | 6 | |
| | 7 | SoapLab is open-source (Apache license?). |
| | 8 | |
| | 9 | LSAE supports a full lifecycle for a job. |
| | 10 | |
| | 11 | * jobID createJob(Map inputs) |
| | 12 | * run(jobID) |
| | 13 | * jobStatus getStatus(jobID) |
| | 14 | * Map getResults(jobID) |
| | 15 | * destroy(jobID) |
| | 16 | |
| | 17 | In the soaplab implementation, a SoaplabMap is used, which restricts the types of the map values to strings, numbers and binary data. |
