fix for operations mapping

A malformed comparison in ```SOAPConnector.prototype._methodName``` resulted in missing or incorrectly mapped SOAP operations to node js object methods.
NOTE:  The return here prevents the default behavior of returning the full operation name in line 136 below, where a SOAP12 method might conflict with the simple method name.  Not sure if this is desired.