修复QueryStopChargeController执行逻辑

This commit is contained in:
wen 2021-11-10 16:26:58 +08:00
parent 8e11f5665d
commit d6697c0bbb

View File

@ -51,10 +51,8 @@ public class QueryStopChargeController {
//判断三方的订单号是否在我们的内部有对应的订单
EtOrderMapping etOrderMapping = etOrderMappingRepo.findByEvcsOrderNo(startChargeSeq).orElse(null);
if (etOrderMapping != null) {
Map<String, Object> pushOrder = new HashMap<>();
pushOrder.put("stopCommandSent", false);
REDIS.setCacheMap("pushOrder:".concat(etOrderMapping.getXhOrderNo()), pushOrder);
if (etOrderMapping == null) {
//充电订单状态
queryStopChargeResponse.setStartChargeSeqStat(5);
//操作结果
@ -72,7 +70,7 @@ public class QueryStopChargeController {
}
CommonResponse commonResponse = new CommonResponse();
commonResponse.setRet("0");
commonResponse.setRet("1");
commonResponse.setMsg("请求停止充电失败:错误的充电订单号");
commonResponse.setData(data);
return commonResponse;
@ -127,7 +125,7 @@ public class QueryStopChargeController {
System.out.println("json转换出问题了");
}
CommonResponse commonResponse = new CommonResponse();
commonResponse.setRet("0");
commonResponse.setRet("1");
commonResponse.setMsg("请求停止充电失败");
commonResponse.setData(data);
}