Marco Roos wrote: > Hello, Hello Marco,
> I wonder, would it be possible to treat empty results as 'potential errors' > in > Taverna, triggering some kind of error or perhaps a warning message with some > tips? When I tried Carsten's xpath example without a namespace the result was > empty, not an error. This is correct I now know, but obviously not what I > expected at first. My guess is that an empty result is often not what people > expect. I'm probably not being inventive, but I think this would require you to specify this small piece of expected behaviour for the service. Taverna would then need to compare the actual behaviour with the expected one and change the output to an ErrorDocument if it didn't match. Would the expected behaviour be the same for each use of the workflow? I can see that if the workflow was nested then what you expect to happen in its services may vary. Also, just applying it to different data sets could alter what you expect to happen. So I'm not sure where this information would be kept. I don't think it's OK to do it as a configuration of the service as that is too static; maybe it needs to be in something that goes along with the workflow run. > Just a thought... It's a good idea. It could be very useful. I've no ideas at the moment how to "architect" it. What do other users think? > Cheers, > Marco. Alan ------------------------------------------------------------------------------ Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev _______________________________________________ taverna-users mailing list [email protected] [email protected] Web site: http://www.taverna.org.uk Mailing lists: http://www.taverna.org.uk/taverna-mailing-lists/
