[
https://issues.apache.org/jira/browse/OFBIZ-2978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abdullah Shaikh updated OFBIZ-2978:
-----------------------------------
Attachment: OFBIZ-2978_gatewayMessage should be pgrMessage.patch
I have changed the service definition to include paymentGatewayRespMsg as
parameter and made both the parameters, paymentGatewayResponse &
paymentGatewayRespMsg optional, and checked which parameter has been passed.
I have created savePgrMessage method, and changed the calling code where
paymentGatewayRespMsg is being passed, now instead of savePgr it will call
savePgrMessage, as we could not decided which parameter is passed in savePgr.
> gatewayMessage should be pgrMessage in savePaymentGatewayResponse of
> PaymentGatewayServices
> -------------------------------------------------------------------------------------------
>
> Key: OFBIZ-2978
> URL: https://issues.apache.org/jira/browse/OFBIZ-2978
> Project: OFBiz
> Issue Type: Bug
> Components: accounting
> Reporter: Abdullah Shaikh
> Assignee: Scott Gray
> Attachments: OFBIZ-2978_gatewayMessage should be pgrMessage.patch,
> OFBIZ-2978_gatewayMessage should be pgrMessage.patch
>
>
> In savePaymentGatewayResponse method of PaymentGatewayServices class, we are
> setting the "gatewayMessage" field on the GenericValue of
> PaymentGatewayRespMsg, but there is no field named "gatewayMessage" in entity
> PaymentGatewayRespMsg but instead we need to use "pgrMessage" in place of
> "gatewayMessage".
> I guess we mistakely assumed the GenericValue which we get from the context,
> context.get("paymentGatewayResponse");, to be of PaymentGatewayResponse, but
> its the GenericValue of PaymentGatewayRespMsg but while putting it on the
> context we named it as "paymentGatewayResponse".
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
