VO(DTO)模式在分层架构设计中是否需要的扯淡

  class XpVO{
     .................
   //<-----上面是一般的vo代码--->
   //下面加一个构造器不就行了?
   public static XpVO createFromPo(XpPo,AccentPo){
   ...............
   }
   public static XpVO changeAccentFromPo(XpPo,AccentPo){
   ...............
   }
}

//第一层：
//基本属性略
private Set<TransportTemplateDetail> transportTemplateDetails = new HashSet<TransportTemplateDetail>();

//第二层：
//基本属性略
private TransportTemplate transportTemplate = new TransportTemplate();
private Set<CustomFreight> customFreights = new HashSet<CustomFreight>();

//第三层：略

	public void addTemplateDetail(List<TransportTemplateDetailVO> transportTemplateDetailList) {
		TransportTemplate transportTemplate = new TransportTemplate();
		try {
			BeanUtils.copyProperties(transportTemplate, transportTemplateDetailList.get(0));
			for (int i = 0; i < transportTemplateDetailList.size(); i++) {
				TransportTemplateDetail transportTemplateDetail = new TransportTemplateDetail();
				BeanUtils.copyProperties(transportTemplateDetail, transportTemplateDetailList
						.get(i));
				transportTemplate
						.addTransportTemplateDetail(transportTemplateDetail);
			}
                           //如果是同一个界面，下面还有一层对象转换。我们分开两个界面来保存。这样还稍微简化了一些东西。
			transportTemplateDao.saveOrUpdate(transportTemplate);
		} catch (IllegalAccessException e) {
			throw new BusinessException("H10001", "转换模板VO失败");
		} catch (Exception e) {
			throw new BusinessException("H10002", "未知异常", e);
		}
	}