[{"_1":2,"_171":-5,"_172":-5},"loaderData",{"_3":4,"_13":14,"_21":22,"_150":151},"root",{"_5":-5,"_6":-7,"_7":8,"_9":-7,"_10":11,"_12":-7},"currentUser","primaryEmail","siteVerification","6LeIxAcTAAAAAJcZVRqyHh71UMIEGNQ_MXjiZKhI","toast","enableDev",false,"incidentStatus","routes/_layout",{"_15":-5,"_16":17,"_18":17,"_19":11,"_20":17},"username","isAskGordonEnabled",true,"isUsingNewTemplate","showMinimalLanding","showHoneypotTrap","routes/_layout.r.$namespace.$reponame",{"_23":24,"_25":-5,"_26":11,"_27":11,"_28":29,"_30":31,"_32":-5,"_33":11,"_34":35,"_84":85,"_103":104,"_141":-5,"_142":11,"_143":17,"_144":11,"_145":-5,"_146":11,"_147":-5,"_148":149},"canonicalUrl","https://hub.docker.com/r/parchapp/soap/tags","mcpServer","canSeeDockerfile","canSeeAutobuilds","namespace","parchapp","reponame","soap","cloudBuildSource","isAutobuildsAvailable","repo",{"_36":37,"_38":39,"_41":42,"_43":44,"_45":11,"_46":47,"_48":49,"_50":51,"_53":31,"_28":29,"_54":55,"_56":40,"_57":58,"_59":60,"_61":62,"_63":-5,"_64":58,"_65":66,"_67":11,"_68":29,"_69":70,"_75":11,"_76":77,"_81":29,"_82":83},"categories",[],"content_types",[40],"image","date_registered","2019-12-20T04:28:41.741467Z","description","","is_private","last_updated","2019-12-20T04:33:37.361267Z","last_modified","2024-10-16T13:48:34.145251Z","media_types",[52],"application/vnd.docker.container.image.v1+json","name","pull_count",129,"repository_type","star_count",0,"status",1,"status_description","active","source","collaborator_count","full_description","# node-soap-example\nA simple SOAP server and client example using the node-soap package and express.\n\n# Introduction\nI'm not an expert in Javascript, nor Node, nor SOAP, but I had the necessity to create a SOAP server using Node.js. Since I found the documentation to be a \nlittle poor, after the time I spent to make things somehow work, I want to share\nwhat I did in case someone else needs this.\n\nThis README will go through a super simple yet kinda comprihensive example to\ncreate a SOAP service and client in Node.js. The service has also been tested and is discoverable using .NET and its service reference tool.\n\n# Example description\nTo show how things work, we will use a very simple example: we want to create a web service that allows a user to split a string message into its components, based on a user defined splitter character.\n\nFor instance, we want the service to split the string \"id1:12:34:56:out42\" using the character \":\" as splitter (which should result into 'id1', '12', '34', '56', 'out42').\n\n# Install\nInstall the required packages by running `npm install` in the project \ndirectory, then you are ready to go.\n\nRun the server with `npm start`, then test it with using the SOAP client with\n`node client.js`.\n\n# Code Explained\nThis section will explain the code, I hope this helps you to understand it better.\n\n## The server\n`app.js` contains the service code. Let's go through it.\n\nWe first define a function named `splitter_function`. This is the function our service will call in order to perform the split.\n\n```\nfunction splitter_function(args) {\n console.log('splitter_function');\n var splitter = args.splitter;\n var splitted_msg = args.message.split(splitter);\n var result = [];\n for(var i=0; iGit README');\n})\n\nvar port = 8000;\n// Launch the server and listen on *port*\napp.listen(port, function () {\n console.log('Listening on port ' + port);\n var wsdl_path = \"/wsdl\";\n // create SOAP server that listens on *path*\n soap.listen(app, wsdl_path, serviceObject, xml);\n console.log(\"Check http://localhost:\" + port + wsdl_path +\"?wsdl to see if the service is working\");\n});\n```\n\nPlease take note of the names we use in `serviceObject` as we will use them again.\nIn this example we use express to launch the server. Other frameworks may work too (eg. loopback).\n\nOther information can be found [here](https://github.com/vpulim/node-soap#soaplistenserver-path-services-wsdl---create-a-new-soap-server-that-listens-on-path-and-provides-services).\n\n## The WSDL\nThis section describes the WSDL file, the file that describes the web service. Some easy and quick information that I found useful can be found [here](https://www.tutorialspoint.com/wsdl/wsdl_introduction.htm).\n\nA service can have multiple publicly available function. For semplicity, we will just define one, named `MessageSplitter`.\n\nSince I had not tool that allowed me to auto generate the WSDL (maybe I'll spend sometime to\ncreate one), I made the WSDL by hand. Please note that I am not an expert in WSDL or SOAP. I created the WSDL file starting from a WSDL file automatically generated from .NET, and used it as a reference to more or less understand how it works. Some parts are obscure to me, but hey, it works!\n\nSo, I'll try to explain the main parts of the WSDL file, without going too much in the details.\n\n### WSDL types\nA web service needs to define its inputs and outputs and how they are mapped into and out of the services. Inside the `` we define the data types the service will use. When we make a request to our function we will need to provide 2 input parameters, both strings. We define the request parameters into ``, and specify the type, name and number of them using ``. For example:\n\n``\n\nmeans that we have a parameter called message, that occurs exacly 1 time, and is of type `string`.\n\nWe then define the output structure creating ``. Notice that the names are not important, we will map later what type need to be considered as input or output.\n\n**IMPORTANT:** the parameters' names need to match those that will be used into the service and client functions (see app.js and client.js):\n\n`app.js`\n```\n[...]\nvar splitter = args.splitter;\nvar splitted_msg = args.message.split(splitter);\n[...]\n```\n\n### WSDL messages\nFollowing the types, we have the messages part. `` describes the data being exchanged between the service and the client. We define two messages, one for the input `MessageSplitterMessageIn`, that refers to the request data type, and one for the output, `MessageSplitterMessageOut`, that refers to the response data type.\n\n```\n\n \n\n\n \n\n```\n\n### WSDL portType\nWe then have the portType, which combines multiple elements to form a complete one-way or round-trip operation.\n\nWe define one single portType ``, that defines one operation which consists of an input and output message, defined above in the WSDL message section.\n```\n\n \n \n\n```\n\n**IMPORTANT:** the `` name has to match the one specified into the service object in the SOAP service definition in `app.js`:\n```\n[...]\nMessageSplitterServiceSoapPort: {\n MessageSplitter: splitter_function\n},\n[...]\n```\n\n### WSDL Binding\nBindings provide details on how a portType operation will actually be transmitted over the wire. There are 2 extremely similar bindings, check them out: they only differ from the version.\n\nWe create a binding with:\n```\n\n```\nthe `name` defines the name of the binding and is not so important, it will referred later. The `type` refers to the port for the binding, and refers to the port we previously defined.\n\nInside the ``, we define a ``:\n```\n\n\n```\nthe `name` and the `soapAction` have to be the same as the name specified in the `` inside the ``, or apparently it does not work (don't know why, I told you there are still a lot of obscure things).\n\nThere 2 very similar bindings in the example.\n\n### WSDL Service\nLast but not least, the `` defines the port supported by the web service. For each supported protocol, there is one port element.\nFrom the service element, clients can learn:\n1. where to access the service\n2. which port to use to access the service\n3. how the communication messages are defined\n\nEach `` has 2 elements: a `name` and a `binding`. The `name` has to be unique among all the ports, the `binding` must refer to a binding previously defined.\n\nNow, recall the service definition in the `app.js` file:\n```\nvar serviceObject = {\n MessageSplitterService: {\n MessageSplitterServiceSoapPort: {\n MessageSplitter: splitter_function\n },\n MessageSplitterServiceSoap12Port: {\n MessageSplitter: splitter_function\n }\n }\n};\n```\nThe `` and the port `` must match the names specified in `app.js`.\n\n## Client\nThe `client.js` file specifies a client.\n```\nvar soap = require('soap');\nvar url = 'http://localhost:8000/wsdl?wsdl';\n\n// Create client\nsoap.createClient(url, function (err, client) {\n if (err){\n throw err;\n }\n var args = {\n message: \"id1:12:34:56:out42\",\n splitter: \":\"\n };\n // call the service\n client.MessageSplitter(args, function (err, res) {\n if (err)\n throw err;\n // print the service returned result\n console.log(res); \n });\n});\n```\nThe file is self-explainatory, just make sure you create the args with the same parameters names specified in the wsdl file.\n\n# References\n1. [https://www.tutorialspoint.com/wsdl](https://www.tutorialspoint.com/wsdl\n2. [https://github.com/vpulim/node-soap](https://github.com/vpulim/node-soap)\n3. [https://github.com/ezzye/nodejs_mock_agresso](https://github.com/ezzye/nodejs_mock_agresso)","has_starred","hub_user","immutable_tags_settings",{"_71":11,"_72":73},"enabled","rules",[74],".*","is_automated","permissions",{"_78":17,"_79":11,"_80":11},"read","write","admin","user","storage_size",366227688,"orgData",{"_86":87,"_88":89,"_90":91,"_92":29,"_93":44,"_94":44,"_95":44,"_96":44,"_97":98,"_99":44,"_100":44,"_101":44,"_102":17},"id","84b91d38c59d4af9876cb62e21d7f03a","uuid","84b91d38-c59d-4af9-876c-b62e21d7f03a","type","organization","orgname","full_name","location","company","profile_url","date_joined","2019-12-14T20:29:14.340319Z","gravatar_url","gravatar_email","badge","is_active","recentTags",[105],{"_106":40,"_107":108,"_109":110,"_86":111,"_112":113,"_46":130,"_131":108,"_132":29,"_133":52,"_53":134,"_135":136,"_137":121,"_138":130,"_139":62,"_140":17},"content_type","creator",8645100,"full_size",366215740,80464394,"images",[114],{"_115":116,"_117":118,"_119":44,"_120":121,"_122":123,"_124":125,"_126":44,"_127":-5,"_128":110,"_59":62,"_129":-5},"architecture","amd64","digest","sha256:94875c8b5a84c4cb0b6c1edfb1c24c8cbce43ddaaabb71603a4e8a947074b508","features","last_pulled","2026-09-23T09:32:54.914116187Z","last_pushed","2019-12-20T04:33:37Z","os","linux","os_features","os_version","size","variant","2019-12-20T04:33:36.988268Z","last_updater","last_updater_username","media_type","latest","repository",8208380,"tag_last_pulled","tag_last_pushed","tag_status","v2","sbxKitMetadata","isPotentialSpam","isHubSbxKitsEnabled","showSbxLogoOverride","sbxTrademarkText","displaySecurityMetadata","tagAttestations","tagsHaveAttestations",[],"routes/_layout.r.$namespace.$reponame.tags",{"_34":152,"_159":160,"_148":169,"_170":11},{"_36":153,"_38":154,"_41":42,"_43":44,"_45":11,"_46":47,"_48":49,"_50":155,"_53":31,"_28":29,"_54":55,"_56":40,"_57":58,"_59":60,"_61":62,"_63":-5,"_64":58,"_65":66,"_67":11,"_68":29,"_69":156,"_75":11,"_76":158,"_81":29,"_82":83},[],[40],[52],{"_71":11,"_72":157},[74],{"_78":17,"_79":11,"_80":11},"tags",{"_161":60,"_162":-5,"_163":-5,"_164":165},"count","next","previous","results",[166],{"_106":40,"_107":108,"_109":110,"_86":111,"_112":167,"_46":130,"_131":108,"_132":29,"_133":52,"_53":134,"_135":136,"_137":121,"_138":130,"_139":62,"_140":17},[168],{"_115":116,"_117":118,"_119":44,"_120":121,"_122":123,"_124":125,"_126":44,"_127":-5,"_128":110,"_59":62,"_129":-5},[],"canDeleteTags","actionData","errors"]

parchapp/soap

Tags for parchapp/soap