topic Re: Method HttpXmlUtility.CheckForErrors() does not parse response properly in Integration and Testing

Method HttpXmlUtility.CheckForErrors() does not parse response properly

vedranmimic — Wed, 11 Feb 2015 17:55:46 GMT

I've experienced problem while working with latest version of AuthorizeNet library (downloaded and built latest source code version from GitHub).

Method CheckForErrors() in HttpXmlUtility class traverses xmlDoc (response) and parses it.

By that algorythm, first child element of document element will be parsed and returned, and it turns to be <messages>...</messages> element, which is wrong; it should be <directResponse>...</directResponse> element, since this is where all data are stored.

Is it a known bug, and when a fix could be expected?

Thanx,

SmartstubsDeveloper

Re: Method HttpXmlUtility.CheckForErrors() does not parse response properly

RaynorC1emen7 — Wed, 11 Feb 2015 20:10:55 GMT

Branch it and fix it.

Re: Method HttpXmlUtility.CheckForErrors() does not parse response properly

vedranmimic — Thu, 12 Feb 2015 10:34:54 GMT

How can i know if only directResponse node should be parsed and returned, or entire xml response?

AuthorizeNet deserializes this xml response into "createCustomerProfileTransactionResponse" or something similar, and all these response classes should be changed if entire xml response needs to be parsed.

I made fix for me locally, just wonder if it will be fixed on master branch, i don't think i can commit code there :)