Fix determining the namespace for complex elements.

Previously, the namespace was only looked up on the schema definition,
while ignoring namespaces defined on the `definitions` element.
Fixup the `elementFormDefault` functionality.

The default for `elementFormDefault` is `unqualified`, unless otherwise
specified. This means we need to treat `qualified` as a special value,
not the other way around.
Added possiblity for request elements containing both content and attributes.
0.4.6 release
0.4.7 release
Using jshint 2.3.0 for indentation.
wsdl should handle more types

* added support for more element types (anyType, SimpleContent,
ComplexContent, choice, extension, all)
* now we need to handle lists correctly even when it has a single
element. This will make it incompatible with previous versions and we
need to increment minor version.
* primitive element value now will be resolved according to the type
Check status code of invocation response
Keep ns from top-level
Ignore unknown elements
Update Readme.md

Updated readme because you get the error "WSSecurity is not defined" with the current example.
Fix: Allow operations to not have definitions
Remove extra characters before and after soap envelope
adding default attributesKey to server and allowing the property to be configurable fixing issue #406
Resolve namespaces correctly by ignoring "tns:", "targetNamespace", "typedNamespace:", ... prefixes in child elements by default.

The ignored namespaces could be easily expanded/overriden by an `ignoredNamespaces` Object within the `options` parameter on `soap.createClient()`.
Updated client.js; Created request-response-sample.
Updating History
0.5.0
Handling nil attributes in response xml
Added possibility to set a custom `valueKey` for the parsed values from XML SOAP Response as the current fixed "$value" key could collide with some policies (as it's the case when using MongoDB).