Add support for optional SOAP options and non-WSDL mode #32
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
Clientconstructor now accepts an array of options. All given options willbe passed through to the underlying
SoapClient. However, not all optionsmake sense in this async implementation and as such may not have the desired
effect. See also
SoapClientdocumentation for more details.
If working in WSDL mode, the
$optionsparameter is optional. If working innon-WSDL mode, the WSDL parameter must be set to
nulland the optionsparameter must contain the
locationandurioptions, wherelocationisthe URL of the SOAP server to send the request to, and
uriis the targetnamespace of the SOAP service:
Builds on top of #31
Resolves / closes #5
Refs #23