On Mon, Sep 27, 2010 at 17:32, Jorge de Jesus <[email protected]> wrote:
> <ExecuteProcess_dummy> > <outputResult1><a></a></outputResult1> > <outputResult2><b></b></outputResult2> > </ExecuteProcess_dummy> > <xsd:schema targetNamespace="http://www.opengis.net/wps/1.0.0";> > <xsd:element > name="ExecuteProcess_ExecuteProcess_dummy"> > <xsd:complexType> > <xsd:sequence> > <xsd:element maxOccurs="1" minOccurs="1" > name="outputResult1" /> > <xsd:element maxOccurs="1" minOccurs="1" > name="outputResult2" " /> You will need to specify the element with type="xsd:any' to allow any XML inside to pass through. A specific type would be even better as it would allow you to connect further XML splitters to delve deeper. As above the schema is saying that there will be an element 'outputResult1' with plain text inside, which does not allow deeper XML elements. If you want to have the option of returning text OR elements, you'll have to use xsd:choice - but Taverna don't have proper support for that at the moment. You could instead wrap the text value in <text>, <value> or equivalent. -- Stian Soiland-Reyes, myGrid team School of Computer Science The University of Manchester ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ 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/
