[MOBY-dev] empty collections

[Edward Kawas]

Hi Jason,

Currently, if a service doesn't have input parameters, it wouldn't be invoked in
Taverna. I will attempt to address this in the very near future! 

It makes complete sense to support services that don't have inputs but do have
outputs.

For my own information, what service are you attempting to use?

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 Jason Reilly
> Sent: Tuesday, December 12, 2006 8:18 AM
> To: moby-dev at lists.open-bio.org
> Subject: [MOBY-dev] empty collections
> 
> Hi all,
> 
> I have encountered an issue and want to get some feedback.  
> The issue is concerning empty collections.  Say, for example, 
> I have a Taverna workflow where a Moby service takes a 
> collection that passes *optional* parameters to the service.  
> In the case I am using, I wrote a blast service where it 
> takes a few parameters like 'database' and 'blastType' 
> (required), as well as a collection of parameters (optional) 
> to be passed to the blast service.  When I run the workflow 
> from Taverna and I leave the input for the collection 
> empty/null, I get an NPE in the generated moby skeleton when 
> it tries to synchronize.  If I just create a collection, but 
> don't populate anything in it, Taverna throws a 
> ServiceFailure ("At least one mobySimple object is needed to 
> build the moby collection") .
> 
> I would propose just wrapping the synchronize block in a not 
> null check, but it would be very easy to create another 
> service....one with parameters and one without.  What is the 
> intent of not allowing empty collections?  Is this a feature or a bug?
> 
> 
> 
> 
> _______________________________________________
> MOBY-dev mailing list
> MOBY-dev at lists.open-bio.org
> http://lists.open-bio.org/mailman/listinfo/moby-dev