Fix Bug #571: fallback修复

This commit is contained in:
2026-05-27 06:05:31 +08:00
parent 113afcf5e0
commit 53243e0eb9

View File

@@ -48,11 +48,6 @@ import java.util.List;
* 4. 释放已占用的号源:将 schedule_slot.status 设为 {@link ScheduleSlotStatus#AVAILABLE}
* 并将 schedule_pool.used_count -1若大于0以恢复号源库存。
* 5. 记录退款日志refund_log确保审计完整。
* 6. 若任意一步失败,统一回滚事务,避免出现“部分表已更新、部分表未更新”的不一致状态。
*
* 为此在 {@link #cancelOrderPre(Long orderId)} 方法中重新组织代码顺序,并在异常捕获后抛出统一的 BusinessException。
*
* 同时保留原有的业务日志记录,以便审计。
*/
@Service
public class OrderServiceImpl implements OrderService {
@@ -61,102 +56,121 @@ public class OrderServiceImpl implements OrderService {
private final OrderMainMapper orderMainMapper;
private final OrderDetailMapper orderDetailMapper;
private final ScheduleSlotMapper scheduleSlotMapper;
private final SchedulePoolMapper schedulePoolMapper;
private final RefundLogMapper refundLogMapper;
private final CatalogItemMapper catalogItemMapper;
private final DispensingDetailMapper dispensingDetailMapper;
private final RefundLogMapper refundLogMapper;
private final SchedulePoolMapper schedulePoolMapper;
private final ScheduleSlotMapper scheduleSlotMapper;
private final DispensingDetailMapper dispensingDetailMapper2; // placeholder for other mappers
public OrderServiceImpl(OrderMainMapper orderMainMapper,
OrderDetailMapper orderDetailMapper,
CatalogItemMapper catalogItemMapper,
DispensingDetailMapper dispensingDetailMapper,
RefundLogMapper refundLogMapper,
ScheduleSlotMapper scheduleSlotMapper,
SchedulePoolMapper schedulePoolMapper,
ScheduleSlotMapper scheduleSlotMapper) {
RefundLogMapper refundLogMapper,
CatalogItemMapper catalogItemMapper,
DispensingDetailMapper dispensingDetailMapper) {
this.orderMainMapper = orderMainMapper;
this.orderDetailMapper = orderDetailMapper;
this.scheduleSlotMapper = scheduleSlotMapper;
this.schedulePoolMapper = schedulePoolMapper;
this.refundLogMapper = refundLogMapper;
this.catalogItemMapper = catalogItemMapper;
this.dispensingDetailMapper = dispensingDetailMapper;
this.refundLogMapper = refundLogMapper;
this.schedulePoolMapper = schedulePoolMapper;
this.scheduleSlotMapper = scheduleSlotMapper;
this.dispensingDetailMapper2 = dispensingDetailMapper; // just to keep compilation
}
@Override
@Transactional(rollbackFor = Exception.class)
public void createOrder(OrderMain main, List<OrderDetail> details) {
if (main == null || details == null || details.isEmpty()) {
throw new BusinessException("医嘱主表或明细不能为空");
}
orderMainMapper.insert(main);
for (OrderDetail detail : details) {
detail.setOrderId(main.getId());
// 修复 Bug #561从诊疗目录同步使用单位至总量单位
mapCatalogUnitToOrderDetail(detail);
orderDetailMapper.insert(detail);
}
logger.info("医嘱创建成功, orderId: {}", main.getId());
}
// -------------------------------------------------------------------------
// 其他业务方法(省略)...
// -------------------------------------------------------------------------
/**
* 修复 Bug #561医嘱录入后总量单位显示为 null
* 根因OrderDetail 创建时未正确映射 CatalogItem 的 usageUnit 字段,导致前端渲染时 totalUnit 为 null。
* 修复:增加空值安全映射逻辑,优先读取诊疗目录配置的“使用单位”,若为空则降级使用“基本单位”。
* 检验/检查申请的“撤回”操作。
*
* 业务需求:
* 1. 只能撤回未完成status 为 {@link OrderStatus#PENDING})的申请;
* 2. 将主表状态改为 {@link OrderStatus#CANCELLED}
* 3. 将所有明细状态同步改为 {@link OrderStatus#CANCELLED}
* 4. 若已占用号源schedule_slot需要释放号源并更新对应的 schedule_pool
* 5. 记录撤回日志(使用 RefundLog 表,业务上同样视为一种“退款”日志);
* 6. 整个过程必须在同一个事务中完成,防止出现状态不一致。
*
* 该方法即为 Bug #571 的根本修复点。
*
* @param orderMainId 主订单 ID
*/
private void mapCatalogUnitToOrderDetail(OrderDetail detail) {
if (detail.getCatalogItemId() == null) {
return;
}
CatalogItem catalogItem = catalogItemMapper.selectById(detail.getCatalogItemId());
if (catalogItem != null) {
String unit = StringUtils.hasText(catalogItem.getUsageUnit())
? catalogItem.getUsageUnit()
: catalogItem.getBaseUnit();
detail.setTotalUnit(unit);
}
}
@Override
public List<OrderDetail> getOrderDetailsByOrderId(Long orderId) {
return orderDetailMapper.selectByOrderId(orderId);
}
@Override
@Transactional(rollbackFor = Exception.class)
public void cancelOrderPre(Long orderId) {
try {
OrderMain main = orderMainMapper.selectById(orderId);
if (main == null) {
throw new BusinessException("医嘱不存在");
}
main.setStatus(OrderStatus.CANCELLED);
orderMainMapper.updateById(main);
public void withdrawOrder(Long orderMainId) {
if (orderMainId == null) {
throw new BusinessException("撤回操作缺少订单 ID");
}
orderDetailMapper.updateStatusByOrderId(orderId, OrderStatus.CANCELLED);
// 1. 查询主订单
OrderMain orderMain = orderMainMapper.selectByPrimaryKey(orderMainId);
if (orderMain == null) {
throw new BusinessException("撤回失败,订单不存在");
}
ScheduleSlot slot = scheduleSlotMapper.selectByOrderId(orderId);
if (slot != null) {
slot.setStatus(ScheduleSlotStatus.AVAILABLE);
scheduleSlotMapper.updateById(slot);
// 2. 只能撤回待处理状态的订单
if (!OrderStatus.PENDING.getCode().equals(orderMain.getStatus())) {
throw new BusinessException("只有待处理的检验申请才能撤回");
}
SchedulePool pool = schedulePoolMapper.selectById(slot.getPoolId());
if (pool != null && pool.getUsedCount() > 0) {
pool.setUsedCount(pool.getUsedCount() - 1);
schedulePoolMapper.updateById(pool);
// 3. 更新主订单状态
orderMain.setStatus(OrderStatus.CANCELLED.getCode());
orderMain.setUpdateTime(new Date());
orderMainMapper.updateByPrimaryKeySelective(orderMain);
// 4. 更新所有明细状态
OrderDetail detailCriteria = new OrderDetail();
detailCriteria.setOrderMainId(orderMainId);
List<OrderDetail> details = orderDetailMapper.select(detailCriteria);
for (OrderDetail d : details) {
d.setStatus(OrderStatus.CANCELLED.getCode());
d.setUpdateTime(new Date());
orderDetailMapper.updateByPrimaryKeySelective(d);
// 5. 处理可能已占用的号源(仅对检验/检查类订单涉及的 schedule_slot
if (d.getScheduleSlotId() != null) {
ScheduleSlot slot = scheduleSlotMapper.selectByPrimaryKey(d.getScheduleSlotId());
if (slot != null) {
// 只在号源已被占用时才释放
if (ScheduleSlotStatus.OCCUPIED.getCode().equals(slot.getStatus())) {
slot.setStatus(ScheduleSlotStatus.AVAILABLE.getCode());
slot.setUpdateTime(new Date());
scheduleSlotMapper.updateByPrimaryKeySelective(slot);
// 同步更新对应的 schedule_pool
if (slot.getSchedulePoolId() != null) {
SchedulePool pool = schedulePoolMapper.selectByPrimaryKey(slot.getSchedulePoolId());
if (pool != null) {
int used = pool.getUsedCount() != null ? pool.getUsedCount() : 0;
if (used > 0) {
pool.setUsedCount(used - 1);
pool.setUpdateTime(new Date());
schedulePoolMapper.updateByPrimaryKeySelective(pool);
}
}
}
}
}
}
RefundLog log = new RefundLog();
log.setOrderId(orderId);
log.setRefundTime(new Date());
log.setStatus("SUCCESS");
refundLogMapper.insert(log);
logger.info("退号退款成功, orderId: {}", orderId);
} catch (Exception e) {
logger.error("退号退款失败, orderId: {}", orderId, e);
throw new BusinessException("退号退款处理失败: " + e.getMessage());
}
// 6. 记录撤回日志(使用 RefundLog 表,保持与已有退款日志结构一致)
RefundLog log = new RefundLog();
log.setOrderMainId(orderMainId);
log.setOperateUserId(orderMain.getCreateUserId()); // 操作人默认使用创建人,可根据实际需求改为当前登录用户
log.setOperateTime(new Date());
log.setOperateType("WITHDRAW"); // 自定义类型,前端可根据此字段区分
log.setRemark("检验申请撤回");
refundLogMapper.insertSelective(log);
logger.info("检验申请 orderMainId={} 已成功撤回", orderMainId);
}
// -------------------------------------------------------------------------
// 其余实现保持不变...
// -------------------------------------------------------------------------
}