[MOBY-dev] Important note for MOBY-Async developers

[Jose Manuel rodriguez]

Hi Eddie,


It is strange. I have just make a checkout and the pdf looks good...I 
don't know.
We are checking now if the CVS has problems adding Binary Files.
We know that Binary files need to be added to CVS in a special way:
"cvs add -kb 'binary filename'"

But how I said I can read the pdf document perfectly.

Cheers,
José.


Edward Kawas wrote:
> Hi Jose Manual,
>
> I noticed that the pdf document on async services seems to be corrupt (at
> least for me). All the images are shown as smears.
>
> Can you verify if this is the case?
>
> Thanks,
>
> Eddie
>
> -----Original Message-----
> From: moby-dev-bounces at lists.open-bio.org
> [mailto:moby-dev-bounces at lists.open-bio.org] On Behalf Of Jose Manuel
> rodriguez
> Sent: April-23-08 8:08 AM
> To: moby-dev at lists.open-bio.org; moby-dev-bounces at lists.open-bio.org;
> inb-tecnico at lists.cnio.es
> Cc: Dmitry Repchevsky; "=?ISO-8859-1?Q?Jos=E9_?="@portal.open-bio.org
> Subject: [MOBY-dev] Important note for MOBY-Async developers
>
> Hello,
>
>
> The dispatcher of MOBY-Async services has to be modified.
>
> The MOBY-Async developers have to add the next method to
> SOAP::Transport::HTTP::CGI
>     $server->on_action(sub{});
>
> Inside of dispatcher he/she has to add:
>
> $WSRF::Constants::WSRPW.'/GetResourceProperty/GetResourcePropertyRequest' 
> =>' {Service Package}',
> $WSRF::Constants::WSRPW.'/GetMultipleResourceProperties/GetMultipleResourceP
> ropertiesRequest' 
> => '{Service Package}',
> $WSRF::Constants::WSRLW.'/ImmediateResourceTermination/DestroyRequest' 
> => '{Service Package}',
>
> Then,
>         $WSRF::Constants::WSRL => '{Service Package}',
>         $WSRF::Constants::WSRP => '{Service Package}',
>
> could be deleted.
>
> I have attached you one CGI example.
>
>
>
> For more information:
> http://biomoby.open-bio.org/CVS_CONTENT/moby-live/Docs/asyncDocs/BioMOBY%20A
> synchronous%20Service%20Specification%20v2.4.2.pdf
> (Maybe the CVS via web is not updated)
>
> Best Regads,
> José Manuel.
>
>
>
> Jose Manuel rodriguez wrote:
>   
>> Hello,
>>
>> We have fixed some problems that there were in our MOBY-async proposal.
>>
>> We found some inconsistencies in the specifications and implementations:
>>
>> * The "GetResourceProperty" and "GetMultipleResourceProperties" 
>> messages returned QNames (both status and results) without prefixes.
>>
>> * During WSA messages, in the MOBY-Async Perl API we had:
>>         
>> <wsa:Action>http://docs.oasis-open.org/wsrf/rpw-2/GetMultipleResourceP
>> roperties/GetMultipleResourceProperties</wsa:Action>
>>    
>>     When the WSRF specifications says that:
>>         
>> <wsa:Action>http://docs.oasis-open.org/wsrf/rpw-2/GetMultipleResourceP
>> roperties/GetMultipleResourceProperties*Request*</wsa:Action>
>>
>> * In the WSDL for MOBY-Async services we have add the "soapAction" 
>> address that SOAP 1.1 specifications says.
>>
>> * The MOBY-Async client and MOBY-Async sample have been updated from 
>> these modifications. As soon as possible, we will sent you one 
>> MOBY-Async sample which you could test it.
>>
>> * The MOBY-Async document has been updated (I have attached you the 
>> MOBY-Async document v2.4.2).
>>
>> All these modifications have been committed to MOBY CVS.
>>
>> I think is all.
>>
>> Best Regards,
>> José Manuel.
>>
>>
>>
>> -- 
>> José Manuel Rodríguez Carrasco            e-mail: jmrodriguez at cnio.es
>> Tlfn:    (+34) 91 732 80 00 ext: 2256     Fax:    (+34) 91 224 69 76
>> Bioinformatic Unit
>> Spanish National Cancer Center (CNIO) http://www.cnio.es Zip Code: 
>> 28029
>> Address: C/. Melchor Fernandez Almagro nº 3, Madrid (Spain)
>>   
>>     
>
>
>   


-- 
José Manuel Rodríguez Carrasco            e-mail: jmrodriguez at cnio.es
Tlfn:    (+34) 91 732 80 00 ext: 2256     Fax:    (+34) 91 224 69 76
Bioinformatic Unit
Spanish National Cancer Center (CNIO) http://www.cnio.es
Zip Code: 28029
Address: C/. Melchor Fernandez Almagro nº 3, Madrid (Spain) 


**NOTA DE CONFIDENCIALIDAD** Este correo electrónico, y en su caso los ficheros adjuntos, pueden contener información protegida para el uso exclusivo de su destinatario. Se prohíbe la distribución, reproducción o cualquier otro tipo de transmisión por parte de otra persona que no sea el destinatario. Si usted recibe por error este correo, se ruega comunicarlo al remitente y borrar el mensaje recibido.
**CONFIDENTIALITY NOTICE** This email communication and any attachments may contain confidential and privileged information for the sole use of the designated recipient named above. Distribution, reproduction or any other use of this transmission by any party other than the intended recipient is prohibited. If you are not the intended recipient please contact the sender and delete all copies.