If you are looking for a way to extract the XML element values as feature attributes, the XMLFlattener or XMLFragmenter might help you.
In addition to what Takashi said, there is also the XMLTemplater in conjunction with the HTTPCaller to construct and transmit the SOAP request.
Further to the other comments, I'd agree that a good way to do this is with a combination of the XMLTemplater to build the request and the HTTPCaller (new name) to post the SOAP request itself. I have attached an example that I built to do a similar request against a road works service, by running in prompt and run mode you can issue all the parameters required by the SOAP service.
roadworksextractor.fmw
More on this and other similar approaches in this webinar:
This article will also help with this workflow (in case any stumbles upon this question looking for more).
https://knowledge.safe.com/articles/45314/working-with-soap-services.html
In addition to what Takashi said, there is also the XMLTemplater in conjunction with the HTTPCaller to construct and transmit the SOAP request.
@david_r I have a problem accessing the results of the xml-fragmenter. I am using a soap service. When I view the data in the inspector I get 39 attributes in the "property" and "value" fields. I am not able to access them with any other transformer or writer. I have manually created the xml file and used a solution proposed by takashi and was able to extract the attributes using an attributekeeper. When using the xml reader the attributes and values were available to the attributekeeper. Why does it not work the same way in xml-fragmenter? I see the attributes and values in the inspector as pairs but not as available fields in the transformer.
Jurgen
@david_r I have a problem accessing the results of the xml-fragmenter. I am using a soap service. When I view the data in the inspector I get 39 attributes in the "property" and "value" fields. I am not able to access them with any other transformer or writer. I have manually created the xml file and used a solution proposed by takashi and was able to extract the attributes using an attributekeeper. When using the xml reader the attributes and values were available to the attributekeeper. Why does it not work the same way in xml-fragmenter? I see the attributes and values in the inspector as pairs but not as available fields in the transformer.
Jurgen
If you're using the XMLFragmenter you'll have to manually specify the attributes to expose in the workspace (you only need to expose the attributes you need working with):
When using the XML Reader, this is done for you automatically, which explains the difference.
