最近接手用 dorado7
来开发一个内容管理系统,生成模板的代码中提示了可以使用 BO 进行数据的操作
有一个问题就是,既然项目中已经有了表的实体类(entity),也有了业务类(service)和数据访问类(DAO),那么 BO 该怎么写?
找了一下相关的资料,终于找到了一篇实际的代码,和大家一起分享:
package com.bstek.dorado.sample.standardlesson.BO;
import java.math.BigDecimal;
import java.util.Collection;
import java.util.HashMap;
import java.util.List;
import java.util.Map;
import org.apache.commons.lang.StringUtils;
import org.hibernate.Query;
import org.hibernate.criterion.Criterion;
import org.hibernate.criterion.DetachedCriteria;
import org.hibernate.criterion.MatchMode;
import org.hibernate.criterion.Restrictions;
import org.springframework.beans.factory.annotation.Autowired;
import org.springframework.stereotype.Service;
import org.springframework.transaction.annotation.Transactional;
import com.bstek.dorado.annotation.DataProvider;
import com.bstek.dorado.annotation.DataResolver;
import com.bstek.dorado.data.provider.Page;
import com.bstek.dorado.data.variant.Record;
import com.bstek.dorado.sample.standardlesson.entity.SlEmployee;
import com.bstek.dorado.sample.standardlesson.hdao.SlEmployeeDao;
@Service
public class EmployeeBO {
@Autowired
private SlEmployeeDao employeeDao;
//employeeBO#getAll
@DataProvider
public Collection<SlEmployee> getAll(){
List<SlEmployee> employees = employeeDao.getAll();
return employees;
}
@DataProvider
//Map<String, Object> parameter
public void getAll(Page<SlEmployee> page,Record parameter){
if(parameter != null){
DetachedCriteria detachedCriteria = DetachedCriteria.forClass(SlEmployee.class);
//员工姓名
String employeeName = (String) parameter.get("employeeName");
if(StringUtils.isNotEmpty(employeeName)){
Criterion criterion = Restrictions.like("employeeName", employeeName, MatchMode.ANYWHERE);
detachedCriteria.add(criterion);
}
//工资>=
BigDecimal salary1 = parameter.getBigDecimal("salary1");
if(salary1 != null){
Criterion criterion = Restrictions.get("salary", salary1);
detachedCriteria.add(criterion);
}
BigDecimal salary2 = parameter.getBigDecimal("salary2");
if(salary2 != null){
Criterion criterion = Restrictions.le("salary", salary2);
detachedCriteria.add(criterion);
}
employeeDao.find(page, detachedCriteria);
}else{
employeeDao.getAll(page);
}
}
@DataProvider
public void getAllByHql(Page<SlEmployee> page,Record parameter){
if(parameter != null){
StringBuilder hql = new StringBuilder(128);
Map<String, Object> parameters = new HashMap<String, Object>();
hql.append("from SlEmployee where 1=1");
String employeeName = parameter.getString("employeeName");
BigDecimal salary1 = parameter.getBigDecimal("salary1");
BigDecimal salary2 = parameter.getBigDecimal("salary2");
if(!StringUtils.isEmpty(employeeName)){
hql.append(" and employeeName like:employeeName");
parameters.put("employeeName", "%"+employeeName+"%");
}
if(salary1 != null){
hql.append(" and salary >=:salary1");
parameters.put("salary1", salary1);
}
if(salary2 != null){
hql.append(" and salary <=:salary2");
parameters.put("salary2", salary2);
}
employeeDao.find(page, hql.toString(), parameters);
}else{
employeeDao.getAll(page);
}
}
@Transactional
@DataResolver
public void saveAll(Collection<SlEmployee> employees) {
// for (SlEmployee e: employees){
// EntityState state = EntityUtils.getState(e);
// System.out.println(state);
// }
employeeDao.persistEntities(employees);
}
@Transactional
@DataResolver
// 可以被前台调用
public void raiseSalary(SlEmployee employee) {
BigDecimal salary = employee.getSalary();
salary = salary.add(BigDecimal.valueOf(1000));
employee.setSalary(salary);
employeeDao.persistEntity(employee);
}
}
由此推断,一般的 BO 需要承载增删改查的功能,查询的方法需要用 @DataProvider
标注,而更新、保存、删除的方法需要用 @DataResolver
标注;如果数据的读写方法需要做成事务,还需要用 @Transactional
标注;
在实体对当前的数据进行操作后,BO 应当调用对应的 DAO 类,将操作过后的实体持久化;
而 BO 更多的应该是对输入的参数进行拼接和处理后,将实体和参数交给对应的 DAO 方法进行操作,而不是重新实现一遍具体的数据操作;
这里有个小技巧,如果可以判断实体的状态为新增或已修改,直接调用 DAO 类的保存方法即可,无需另外编写更新实体的方法;
如果一定要实现更新实体的方法,该方法必须接收一个原有的实体,还有需要修改的属性;在修改实体后,将实体的状态改成已修改,然后将这个实体持久化;