Re: Error in Service [releaseOrderPaymentPreference]: Problem releasing payment

[Scott Gray]

Your fix probably failed because releaseAmount is required by the service that is being called. If no authTransaction is found I guess there isn't much point in trying to release it anyway.

But from there a couple of question arise as to what the actual bug is:



Regards
Scott

HotWax Media
http://www.hotwaxmedia.com

On 16/11/2009, at 11:49 AM, Jacques Le Roux wrote:

- Is the authTransaction present and just not being correctly searched for? - Should releaseOrderPaymentPreference be called if there is no authorized transaction? The code appears to assume the payment pref is in an authorized state so the check must be taking place earlier.

While trying to edit DEMO10090 order items I got an NPE in


I fixed it using
      if (UtilValidate.isNotEmpty(authTransaction)) {

      } else {
          releaseContext.put("releaseAmount", null);
      }


I gave up at this stage. What could be the reason ?

Thanks

Jacques

releaseOrderPaymentPreference[917] releaseContext.put("releaseAmount", authTransaction.getBigDecimal("amount")); releaseContext.put("releaseAmount", authTransaction.getBigDecimal("amount")); But then I got Error in Service [releaseOrderPaymentPreference]: Problem releasing payment

smime.p7s
Description: S/MIME cryptographic signature