On Tue, Dec 1, 2009 at 09:38, Linda Bakker <[email protected]> wrote: > The problem that I am having is with optional parameters. In my wsdl > file, the parameterOrder is the following: > parameterOrder="datatype species genenames dataset sgi_corr_cutoff > sgi_inter_cutoff ppi_conf_cutoff" The first 3 are mandatory and the last > 4 are optional. If for example I decide to use the last optional > parameter, the first three optional input parameters should be marked as > empty and my value should be linked to the last field. In stead, the > value gets associated with the first optional input field. This happens > because
You don't specify in the WSDL that the parameter is optional, only: <wsdl:documentation>optional</wsdl:documentation> The wsdl:documentation is free text, so Taverna (or any other WSDL framework) can't understand that this means it is actually optional. As far as I know it is not possible to set minOccurs="0" for message parts, and even if it was I'm not sure how this would be interpreted when you have added a specific parameterOrder. The recommended way to do this these days is to do a Wrapped Document/Literal service with just a single part that is a complex type, and in the complex type you can define various elements to be optional or not using minOccurs. -- Stian Soiland-Reyes, myGrid team School of Computer Science The University of Manchester ------------------------------------------------------------------------------ Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev _______________________________________________ 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/
