Ws.js - A ws-* Implementation of Node.js
(Get Ws.js on github)
Some time ago I introduced Wcf.js - a wcf-inspired client soap stack for node.js. However Wcf.js itself is a small wrapper on top of Ws.js - the ws-* implementation for node.js. You got it right: Your node.js apps can now access your core services using various ws-* standards. No more proxies for "protocol bridging", no more service rewrites.
Get it here.
Here is a quick sample on what we can do with Ws.js:
The above example adds a username token to the soap. The output soap will be:
For detailed usage instructions check it out on github.
Ws.js currently supports:
MTOM
WS-Security (username tokens only)
WS-Addressing (all versions)
HTTP(S)
Coming up next is probably deeper ws-security support including x.509 certificates encryption and signature. Needless to say that any capability added to ws.js will also apply to wcf.js.
Here is the project page on github.
Published at DZone with permission of Yaron Naveh, author and DZone MVB. (source)Some time ago I introduced Wcf.js - a wcf-inspired client soap stack for node.js. However Wcf.js itself is a small wrapper on top of Ws.js - the ws-* implementation for node.js. You got it right: Your node.js apps can now access your core services using various ws-* standards. No more proxies for "protocol bridging", no more service rewrites.
Get it here.
Here is a quick sample on what we can do with Ws.js:
The above example adds a username token to the soap. The output soap will be:
For detailed usage instructions check it out on github.
Ws.js currently supports:
Coming up next is probably deeper ws-security support including x.509 certificates encryption and signature. Needless to say that any capability added to ws.js will also apply to wcf.js.
Here is the project page on github.
(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)





