On Mon, Aug 9, 2010 at 10:36, Anja Le Blanc <[email protected]> wrote: > Here an update on our VOTable loop problem. We changed one of our > services > (http://msslxw.mssl.ucl.ac.uk:8080/helio-ics-votable/HelioServiceVotable2?wsdl) > to use VOTable v1.2 which has a modified version of the loop: > > <xs:complexType name="Option"> > <xs:sequence> > <xs:element name="OPTION" type="Option" minOccurs="0" > maxOccurs="unbounded"/> > </xs:sequence> > <xs:attribute name="name" type="xs:token"/> > <xs:attribute name="value" type="xs:string" use="required"/> > </xs:complexType> > > That should be less nasty then before, but still does not work with Taverna.
It seems that Axis1 (which does Taverna's WSDL parsing) unfortunately still is not happy and complains about loop. This is a bit weird, because I'm certain I've seen such recursive complex types before, typically anything with a 'parent' type. (I even remember a warning dialogue about the recursion.) So Taverna itself should supports this, I'm looking to find out how those WSDLs did recursion. -- Stian Soiland-Reyes, myGrid team School of Computer Science The University of Manchester ------------------------------------------------------------------------------ This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd _______________________________________________ taverna-users mailing list [email protected] [email protected] Web site: http://www.taverna.org.uk Mailing lists: http://www.taverna.org.uk/about/contact-us/
