2009/3/25 Marco Roos <[email protected]>: > * Could the list depths of a beanshell be correct in principle, but that it > gets a different input than expected while Taverna1 deals with it somehow > instead of giving an error?
What probably happens is that something goes wrong and returns this string instead of failing. Can you reproduce this error in Taverna 2.0? Also double-check your iteration strategies - in Taverna 1 these can become disconnected and wrong if you have later changed the ports (like on a beanshell or nested workflow). > * Can Web Services introduce these type of errors too? Or are they by > definition strict on e.g. the list depth of their output? They are normally strict on this, if the schema/wsdl says it will return a list, but a single value is returned, that will look the same on the wire (a "list" is just several repetitions of the same element in the XML), and you'll get a list of one item. If the schema says it will return a single value, but several are returned, I'm not sure what happens, but I believe only the first one is sent on. -- Stian Soiland-Reyes, myGrid team School of Computer Science The University of Manchester ------------------------------------------------------------------------------ Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com _______________________________________________ taverna-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/taverna-users Documentation: http://www.mygrid.org.uk/usermanual1.7/ FAQ: http://www.mygrid.org.uk/wiki/Mygrid/TavernaFaq Biological Services: http://www.mygrid.org.uk/wiki/Mygrid/BiologicalWebServices
