Details
-
Bug
-
Status: To Do
-
Major
-
Resolution: Unresolved
-
None
-
None
Description
The problem is in a way the splitter decides whether there are any elements to split:
AbstractAddXMLSplitterAction.filterDescriptors()
The decision is taken based on element "mime" type.
In the example wsdl there is a case
<xs:element name="string_array" type="xs:string" form="qualified" minOccurs="0" maxOccurs="unbounded"/>
The type recognized by Taverna is String[] with a mime type being "text/plain". The problem is that Taverna sees it as a single property.
I am not sure how Taverna it is supposed to act. It may not filter these "unbounded" elements, or edit multiple values in property editor.
The problem exists in Tav 2.4 and 3.0.