Re: [Soaplab2-dev] Re: acd development terms
Brought to you by:
marsenger
From: Peter E. <P....@dk...> - 2006-05-31 13:28:31
|
On Wed, 31 May 2006, Mahmut Uludag wrote: > Can you please give brief information about the Soaplab <-> Applab > issues that prevented the use of the XML schema? The data transfer between Soaplab and Applab is realised with a HashMap. But this means, that the order of the parameters on the command-line gets lost. For example, in the Emboss program "water", you can have two times the parameter "sformat": $ water -sformat=gcg seq1.gcg -sformat=fasta seq2.fa In order to distinguish between both "sformat"s, SoapLab uses the alernative notation: -sformat1=... and -sformat2=... But therefore I couldn't reference an external Emboss/Acd type like this: <xs:complexType name="Tsequence"> <xs:simpleContent> <xs:extension base="xs:string"> <xs:attribute name="sbegin" type="xs:integer" use="optional"/> <xs:attribute name="send" type="xs:integer" use="optional"/> <xs:attribute name="sformat" type="xs:string" use="optional"/> [....] </xs:extension> </xs:simpleContent> </xs:complexType> Different types must be created for sformat1 and sformat2. See http://genome.dkfz-heidelberg.de/menu/hobit/embapps/wsdl/water.wsdl for an example. The problem disappears, when the order of the parameters on the command-line is defined, and doesn't get lost. I guess this is something that must be fixed anyway, because it is not so unusal, that the order of the parameters on the command-line matters for a tool. Kind regards, Peter |