file: jquery.soap.js
version: 1.7.3
Note that all options are optional. To actually send a request url en data are the minimal requirements. More general information about the usage of jQuery.soap
type: boolean
default: true
Indicates whether the specified method should be added to the url
$.soap({
url: 'http://server.com/webServices/',
method: 'getItem',
appendMethodToURL: false
})
will send a request to http://server.com/webServices/
type: boolean
default: true
available since: 1.3.0
Set to false when you want the
Note that most browsers will throw a warning when using async: false
!
Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user’s experience. For more help http://xhr.spec.whatwg.org/
type: function(SOAPEnvelope)
available since: 1.3.1
Callback function which passes back the SOAPEnvelope object prior to the $.ajax call. From version 1.4.0 returning false in the beforeSend
function will cancel the request.
$.soap({
beforeSend: function(SOAPEnvelope) {
console.log(SOAPEnvelope.toString());
}
});
type: any
default: the $.ajax settings
available since: 1.5.0
Used to set this
in beforeSend
, success
, error
and data
callback functions. This setting mimics the behavior of context in jquery.ajax
$.soap({
context: document.body,
success: function(SOAPResponse) {
console.log(this);
}
});
type: string or XMLDOM or JSON or function(SOAPObject)
default: null
available since: 1.3.0
The data to be sent to the WebService, mainly the contents of the soap:Body, although it may also contain the complete soap:Envelope (with optional soap:Header).
In the first example var xml
is an array of strings which is joined together to form one XML string which is used as the data
.
var xml =
['<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope/">',
'<soap:Body>',
'<requestNode>',
...
'</requestNode>',
'</soap:Body>',
'</soap:Envelope>'];
$.soap({
data: xml.join('')
});
But it is also allowed to just pass in the XML that should go in the body, the envelope and body node will be generated by $.soap for you:
var xml =
['<requestNode>',
'<name>Remy Blom</name>',
'<msg>Hi!</msg>',
'</requestNode>'];
$.soap({
data: xml.join('')
});
In the following example we use JSON to describe the request element.
$.soap({
method: 'requestNode',
data: {
name: 'Remy Blom',
msg: 'Hi!'
}
});
will result in:
<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope/">
<soap:Body>
<requestNode>
<name>Remy Blom</name>
<msg>Hi!</msg>
</requestNode>
</soap:Body>
</soap:Envelope>
In this example data
is a function receiving $.soap's SOAPObject that can be used to create and return an instance of the SOAPObject class.
$.soap({
data: function(SOAPObject) {
return new SOAPObject('soap:Envelope')
.addNamespace('soap', 'http://schemas.xmlsoap.org/soap/envelope/')
.newChild('soap:Body')
... etc, etc
.end()
}
});
will result in:
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
...
</soap:Body>
</soap:Envelope>
From version 1.7.2 it is also possible to set data
to a string to set the value of a bare parameter. Keep in mind it is only possible to set one bare parameter this way. Use of <
is not possible inside the value.
$.soap({
method: "bareParameter",
data: "bare parameter value",
namespaceQualifier: "myns",
namespaceURL: "https://myns.com"
});
will result in:
<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope/">
<soap:Body>
<myns:bareParameter xmlns:myns="https://myns.com">bare parameter value</myns:bareParameter>
</soap:Body>
</soap:Envelope>
type: object
default: null
Set additional attributes (like namespaces) on the soap:Envelope node
$.soap({
envAttributes: {
'xmlns:another': 'http://anotherNamespace.com/'
}
})
will result in:
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:another="http://anotherNamespace.com/">
...
</soap:Envelope>
type: string
default: method
Overrides method as the name for the request element.
This option ONLY applies when the request XML is going to be built from JSON data.
$.soap({
method: 'helloWorld',
elementName: 'requestNode'
})
will result in:
<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope/">
<soap:Body>
<requestNode>
...
</requestNode>
</soap:Body>
</soap:Envelope>
type: boolean
default: false
available since: 1.0.5
Set to true if you want some debug information in the console about the information send and received, errors and globalConfig updates.
$.soap({
enableLogging: true
})
type: function(SOAPResponse)
Allows to set a callback function for when the underlying $.ajax call goes wrong.
Note that $.soap() also returns a jqXHR object that implements the Promise interface, so instead of the error option you can also use jqXHR.fail()
.
$.soap({
error: function(SOAPResponse) {
console.log(SOAPResponse.toString());
}
});
type: object
default: null
available since: 1.3.0
Set additional http request headers. A possible use is setting the Authorization
header to do HTTP Basic Authorization as in the example below.
This setting is directly fed to the $.ajax call as headers withing $.soap and should perform equally.
More info: jquery.ajax
$.soap({
HTTPHeaders: {
'Authorization': 'Basic ' + btoa('user:pass')
}
}):
type: string
The service operation name.
- Will be appended to the url by default unless appendMethodToURL is set to false.
- Will be used to set SOAPAction request header unless a SOAPAction is specified
- When data is specified as JSON
method
will be used for the request element name unless a elementName is provided.
$.soap({
url: 'http://server.com/webServices/',
method: 'getItem'
})
will result in:
<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope/">
<soap:Body>
<getItem>
...
</getItem>
</soap:Body>
</soap:Envelope>
send to http://server.com/webServices/getItem
.
type: string
default: null
Used as namespace prefix for all elements in the request element, in combination with namespaceURL
This option ONLY applies when the request XML is going to be built from JSON data.
$.soap({
method: 'helloWorld',
namespaceQualifier: 'myns',
namespaceURL: 'urn://service.my.server.com'
});
will result in:
<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope/">
<soap:Body>
<myns:helloWorld xmlns:myns="urn://service.my.server.com">
...
</myns:helloWorld>
</soap:Body>
</soap:Envelope>
type: string
default: null
Used as the namespace url added to the request element in combination with namespaceQualifier. From version 1.3.6 it also possible to supply only the namespaceURL.
This option ONLY applies when the request XML is going to be built from JSON data.
$.soap({
method: 'helloWorld',
namespaceQualifier: 'myns',
namespaceURL: 'urn://service.my.server.com'
});
will result in:
<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope/">
<soap:Body>
<myns:helloWorld xmlns:myns="urn://service.my.server.com">
...
</myns:helloWorld>
</soap:Body>
</soap:Envelope>
type: boolean
default: false
available since: 1.2.0
Set to true if you don't want the namespaceQualifier to be the prefix for the nodes in the request element.
This option ONLY applies when the request XML is going to be built from JSON data.
$.soap({
method: 'helloWorld',
namespaceQualifier: 'myns',
namespaceURL: 'urn://service.my.server.com',
noPrefix: true
});
will result in:
<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope/">
<soap:Body>
<helloWorld xmlns:myns="urn://service.my.server.com">
...
</helloWorld>
</soap:Body>
</soap:Envelope>
type: boolean
default: false
Set to true if you want to sent a SOAP1.2 compatible soap:Envelope with SOAP1.2 namespace
$.soap({
soap12: true
})
will result in:
<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope/">
...
</soap:Envelope>
type: string
default: method
Allows to manually set the HTTP Request Header 'SOAPAction'.
$.soap({
url: 'http://server.com/webServices/',
method: 'getItem',
SOAPAction: 'getAnItem'
})
type: string or XMLDOM or JSON or function(SOAPObject)
Allows to set the SOAP:Header. More info on different options see data
$.soap({
SOAPHeader: {
test: [1,2,3]
}
})
will result in:
<soap:Envelope>
<soap:Header>
<test>1</test>
<test>2</test>
<test>3</test>
</soap:Header>
<soap:Body>
...
</soap:Body>
</soap:Envelope>
type: object
available since: 1.6.0
An object of numeric HTTP codes and functions to be called when the response has the corresponding code. This setting is directly fed to the
$.soap({
statusCode: {
404: function() {
console.log('404 Not Found')
},
200: function() {
console.log('200 OK')
}
}
});
type: function(SOAPResponse)
Callback function to handle successful return.
Note that $.soap() also returns a jqXHR object that implements the Promise interface, so instead of the success option you can also use jqXHR.done()
.
$.soap({
success: function(SOAPResponse) {
console.log(SOAPResponse.toString());
}
});
type: number
default: 5000
available since: 1.7.0
Set a timeout (in milliseconds) for the request. This setting is directly fed to the $.ajax call and should perform equally. More info: jquery.ajax
$.soap({
timeout: 100
});
type: string
Specifies the endpoint of the webService. By default the method is added to the url. Setting appendMethodToURL to false will not add the method.
$.soap({
url: 'http://server.com/webServices/',
method: 'getItem'
})
type: bool
default: true
available since: 1.6.11
Set to false when you want the $.ajax call to be send without credentials. This setting is directly fed to the $.ajax call by the xhrFields and should perform equally. More info: jquery.ajax
type: object
available since: 1.1.0
To create a soap:Header with credentials for WS-Security
$.soap({
wss: {
username: 'user',
password: 'pass',
nonce: 'w08370jf7340qephufqp3r4',
created: new Date().getTime()
}
});
will result in:
<soap:Envelope>
<soap:Header>
<wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
<wsse:UsernameToken>
<wsse:Username Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">user</wsse:Username>
<wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">pass</wsse:Password>
<wsse:Nonce Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">aepfhvaepifha3p4iruaq349fu34r9q</wsse:Nonce>
<wsu:Created Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">1383257509878</wsu:Created>
</wsse:UsernameToken>
</wsse:Security>
</soap:Header>
<soap:Body>
...
</soap:Body>
</soap:Envelope>
To keep the names of the options a bit more consistent with common naming conventions I renamed a few options:
old | new | reason |
---|---|---|
namespaceUrl | namespaceURL | to capitalize URL is quite common |
params | data | $.ajax uses data too, more consistent |
request | beforeSend | $.ajax uses beforeSend too, more consistent |
The old names are mapped to the new names and will be removed at version 2.0.0 (that might take years, or decades). A warning is printed to the console when you use an old name.