[moby] [MOBY-dev] Registrying a moby service that takes an input collection

[Arnaud Kerhornou]

Edward Kawas wrote:

>Hi,
>
>This is happening, because Taverna is expecting an object
>type of DNASequence, yet CommentedDNASequence is being
>passed in.
>
>  
>
okay, maybe i should have asked this before, the service returns 
CommentedDNASequence objects, and the service specs say DNASequence 
objects, but CommentedDNASequence is-a DNASequence.

I designed the service to return DNASequence objects. Then a user asked 
me to add a description foreach sequence the service returns, so i just 
changed the type of object the service returns to CommentedDNASequence 
and I didn't changed the specification of the service because i thought 
i didn't have to.

Does it mean it is not allowed to do so ?

I have a similar problem with the next service in my workflow. This 
service analyzes DNASequence objects. But i get CommentedDNASequence 
objects from the retrieval service. Again i can not do that ?

Arnaud

>Eddie
>
>  
>
>>-----Original Message-----
>>From: Arnaud Kerhornou [mailto:akerhornou at imim.es]
>>Sent: Monday, November 07, 2005 6:47 AM
>>To: Edward Kawas
>>Subject: Re: [moby] [MOBY-dev] Registrying a moby service
>>that takes an input collection
>>
>>ok, so i could modify my workflow to connect the
>>DNASequence
>>(Collection) output port to the input port of the next
>>node.
>>
>>but why, in the case i use the port that says collection,
>>do i get an
>>empty collection tag,
>>
>>* "DNASequence (Collection)" gives me:
>>
>> <moby:MOBY xmlns:moby="http://www.biomoby.org/moby">
>>      <moby:mobyContent>
>>           <moby:mobyData moby:queryID="a1">
>>                <moby:Collection
>> moby:articleName="upstream_sequences" />
>>           </moby:mobyData>
>>      </moby:mobyContent>
>> </moby:MOBY>
>>
>>why are the simples missing ?
>>
>>Arnaud
>>
>>
>>    
>>
>  
>