Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixes spelling error in WSSecurityCert-section. #917

Merged
merged 1 commit into from
Feb 9, 2017
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
30 changes: 15 additions & 15 deletions Readme.md
Original file line number Diff line number Diff line change
Expand Up @@ -436,18 +436,18 @@ client.MyService.MyPort.MyFunction({name: 'value'}, options, extraHeaders, funct
Client instances emit the following events:

* request - Emitted before a request is sent. The event handler receives the
entire Soap request (Envelope) including headers. The second parameter is the exchange id.
entire Soap request (Envelope) including headers. The second parameter is the exchange id.
* message - Emitted before a request is sent. The event handler receives the
Soap body contents. Useful if you don't want to log /store Soap headers. The second parameter is the exchange id.
Soap body contents. Useful if you don't want to log /store Soap headers. The second parameter is the exchange id.
* soapError - Emitted when an erroneous response is received.
Useful if you want to globally log errors.
The second parameter is the exchange id.
The second parameter is the exchange id.
* response - Emitted after a response is received. The event handler receives
the SOAP response body as well as the entire `IncomingMessage` response object.
The third parameter is the exchange id.
The third parameter is the exchange id.
This is emitted for all responses (both success and errors).

An 'exchange' is a request/response couple.
An 'exchange' is a request/response couple.
Event handlers receive the exchange id in all events.
The exchange id is the same for the requests events and the responses events, this way you can use it to retrieve the matching request
when an response event is received.
Expand All @@ -458,7 +458,7 @@ Example :

```javascript
client.MyService.MyPort.MyFunction(args , function(err, result) {

}, {exchangeId: myExchangeId})
```

Expand Down Expand Up @@ -526,7 +526,7 @@ WS-Security X509 Certificate support.
client.setSecurity(wsSecurity);
```

_Note_: Optional dependency 'ursa' is required to be installed succefully when WSSecurityCert is used.
_Note_: Optional dependency 'ursa' is required to be installed successfully when WSSecurityCert is used.

## Handling XML Attributes, Value and XML (wsdlOptions).
Sometimes it is necessary to override the default behaviour of `node-soap` in order to deal with the special requirements
Expand Down Expand Up @@ -660,32 +660,32 @@ To do so, you can pass an customDeserializer object in options. The properties o

Example :
```javascript

var wsdlOptions = {
customDeserializer = {

// this function will be used to any date found in soap responses
date: function (text, context) {
/* text is the value of the xml element.
context contains the name of the xml element and other infos :
{
context contains the name of the xml element and other infos :
{
name: 'lastUpdatedDate',
object: {},
schema: 'xsd:date',
id: undefined,
nil: false
nil: false
}

*/
return text;
}
}
};

soap.createClient(__dirname + '/wsdl/default_namespace.wsdl', wsdlOptions, function (err, client) {
...
});

```

## Handling "ignored" namespaces
Expand Down