Discussion: Make soap-server operations async

[morganrallen]

Currently calling operations is done synchronously. Not only is this just not the Node way it makes it impossible to use outside async services.
I am working with a client who is using node-soap-server as an API endpoint which is require to call an external services for part of its response. I have had to hack in a solution that I do not feel is adequate. I am interested in hearing opinions on improving this moving forward and making it more Node-like.

[tan-tan-kanarek]

Sure, just fork it.

T.

From: morganrallen [mailto:[email protected]]
Sent: Friday, February 7, 2014 10:43 PM
To: tan-tan-kanarek/node-soap-server
Subject: [node-soap-server] Discussion: Make soap-server operations async (#3)

Currently calling operations is done synchronously. Not only is this just not the Node way it makes it impossible to use outside async services.
I am working with a client who is using node-soap-server as an API endpoint which is require to call an external services for part of its response. I have had to hack in a solution that I do not feel is adequate. I am interested in hearing opinions on improving this moving forward and making it more Node-like.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/3.

[MauriceButler]

@morganrallen Did you make this change already? If not im probably going to do the same thing if it helps

[morganrallen]

@MauriceButler
No, the original code is far too messy to warrant a fork, I did hack in a 'good enough' solution for the client. DM me if you want some direction on that.

[MauriceButler]

@morganrallen I actually came to the same conclusion, I did however find this library did async Soap server (as well as client)

https://www.npmjs.org/package/soap

It dosnt do the automagical wsdl generation but it actually works.