Soaplab   What ToDo next...

  • Soaplab 2

    Soaplab is old enough to think about a major change (backward compatible, don't worry). This is also related to a new OMG standard Life Sciences Analysis Engine. The current Soaplab is already a prototype of this specification but in order to be fully compliant it needs few more features:

    • Adding a notification service. The AppLab produces events using CosEvent CORBA service and the Soaplab should be able to accept them and propagate them to the clients using a negotiated notification protocol.

    • Adding possibility to send and retrieve data by chunks (to apply an Iterator pattern).

    The Life Sciences Analysis Engine specification is available in documents:

    lifesci/04-08-10
    lifesci/04-08-11

  • SOWA - Soaplab without AppLab

    A brand new Soaplab implementation that would not use internally any CORBA. (But the current implementation will still stay for those who wish to distribute Soaplab services on more machines - for that CORBA is suitable.)

    Actually, this may be part of the Soaplab2 project mentioned earlier.

  • Provide scripts/programs to clean up mySQL database (to remove old results), and to check automatically if all servers are running properly (a candidate for being a cron job). Actually, the cleaning script is there already but it has not been fully tested.

  • Finish the Registry client that can fully register Soaplab services with the existing service repositories (such as BioMoby). Or perhaps even to generate BioMoby compliant web services.

  • Few other things, regarding Gowlab, is mentioned on its own page in the chapter about plug-ins.

  • And, of course, fix the known issues:
    • The Admin client (used for deploying services) does not work yet with Java 1.5 (it seems that the problem is within Apache Axis).
    • Sometimes the connection pool to mySQL seems to be broken.

    • Finish the ACD Guide...

Martin Senger
Last modified: Mon Apr 25 12:18:11 2005