integreat-io / integreat-adapter-soap Goto Github PK

endpoint.path is used to both retrieve part of the data from a response, and set the data with parent objects for a request. This does not make sense with SOAP, as the request and response are seen as independent SOAP messages, even though one comes as response to the other.

A path can be helpful in both cases, but it should be possible to set them independently. Or perhaps it should just be reserved for the response ...?

When an entry has attributes, like namespaces, and the child is a text node, the attributes and the text node are set as properties on an object, with _text as the key for the text node.

Should it be possible to have a path to the entry and receive the content of _text, just as if it had no attributes?

The strangest effect of this, is when a namespace is removed during normalisation, but _text is kept as the only property on the element object. Should we transform the object to the content of _text in these cases?

SOAP 1.1:

{
  SOAPAction: 'http://tempuri.org/HelloSimple',
  'Content-Type': 'text/xml; charset=utf-8'
}

SOAP 1.2:

{
  'Content-Type': 'application/soap+xml;charset=utf-8;action="http://tempuri.org/HelloSimple"'
}