You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have issue with multiple parameters in soap function call. I can assign parameters as objects to function and using native SoapClient I can create working request like this:
Now, with Soap::to this is not possible as __call() accepts only first parameter resulting xml missing files part. This is how I thought it should work:
Is it possible to add support for multiple parameters (not just array) in __call method to make it work more like php's native SoapClient function call?
The text was updated successfully, but these errors were encountered:
Sounds like you know what you're doing here. Any chance you could create a PR with tests? I'd be happy to accept. If not, we're a little rushed off our feet at the moment, so my answer is "yes, but I can't give you a timeframe".
I have issue with multiple parameters in soap function call. I can assign parameters as objects to function and using native SoapClient I can create working request like this:
Now, with Soap::to this is not possible as
__call()
accepts only first parameter resulting xml missingfiles
part. This is how I thought it should work:Also notice, that $apiKeys and $files are objects:
And here is the wsdl:
Here is expected soap request:
Is it possible to add support for multiple parameters (not just array) in
__call
method to make it work more like php's native SoapClient function call?The text was updated successfully, but these errors were encountered: