Re: [Soaplab-users] ACD outfile problem: how do you return a file? (soaplab2)

[Tom C. <tc...@cs...>]

Mahmut Uludag wrote:
>> I'm trying to expose a Java program as a web service using soaplab2
>> (2.1.1), but I am unable to return the wav audio output file that it
>> generates. It uses a -dumpAudio flag to output to a file, otherwise the
>> audio is played on the server (sent to the audio stream - not ideal for
>> a web service). This is how I have encoded the dumpAudio parameter in
>> the ACD file:
>>
>> # -dumpAudio <file> flag
>> string: dump_audio [
>>   qualifier: dumpAudio
>>   standard: "Y"
>>   default: "output.wav"
>>   information: "dump audio to this file (default: output.wav)"
>>   comment: defaults
>>   comment: "display false"
>> ]
>>
>> it's hidden from the user so will always output to a file. My outfile
>> definition is:
>>
>> outfile: output [
>>   comment: "mimetype audio/x-wav"
>>   comment: bindata
>>   comment: "make_url yes"
>> ]
> 
> It looks like you should combine above two options into one. your Java
> programs output seems not connected to the Soaplab service output. You
> should have something similar to the following option.
> 
> # -dumpAudio <file> flag
> outfile: dump_audio [
>   qualifier: dumpAudio
>   standard: "Y"
>   default: "output.wav"
>   information: "dump audio to this file (default: output.wav)"
>   comment: defaults
> #  comment: "display false"
>   comment: "mimetype audio/x-wav"
>   comment: bindata
>   comment: "make_url yes"
> ]

That works great Mahmut, thanks. The soaplab2 docs are slightly
confusing with regards to how outfiles work, but this definitely makes
sense now! Martin Senger also replied to an email I sent to the
soaplab2-dev list, which reiterated how one should think about
parameters, inputs and outputs of soaplab2 services.

Regards,

Tom