我自己在这篇文章中很快回答了这个问题,但是我们花了两周时间尝试不同的策略来克服这个问题.所以,这是我们决定使用的最终实现.
基本思想:通过扩展Hibernate给出的一个来创建自己的javax.persistence.spi.PersistenceProvider实现.对于所有效果,这是您的代码与Hibernate或任何其他供应商特定实现相关联的唯一点.
public class MyHibernatePersistenceProvider extends org.hibernate.jpa.HibernatePersistenceProvider {
@Override
public EntityManagerFactory createContainerEntityManagerFactory(PersistenceUnitInfo info, Map properties) {
return new EntityManagerFactoryWrapper(super.createContainerEntityManagerFactory(info, properties));
}
}
我们的想法是使用您自己的实现来包装hibernate的EntityManagerFactory和EntityManager版本.因此,您需要创建实现这些接口的类,并将供应商特定的实现保留在其中.
这是EntityManagerFactoryWrapper
public class EntityManagerFactoryWrapper implements EntityManagerFactory {
private EntityManagerFactory emf;
public EntityManagerFactoryWrapper(EntityManagerFactory originalEMF) {
emf = originalEMF;
}
public EntityManager createEntityManager() {
return new EntityManagerWrapper(emf.createEntityManager());
}
// Implement all other methods for the interface
// providing a callback to the original emf.
EntityManagerWrapper是我们的拦截点.您需要从界面实现所有方法.在可以修改实体的每个方法中,我们都包含对自定义查询的调用,以在数据库中设置局部变量.
public class EntityManagerWrapper implements EntityManager {
private EntityManager em;
private Principal principal;
public EntityManagerWrapper(EntityManager originalEM) {
em = originalEM;
}
public void setAuditVariables() {
String userid = getUserId();
String ipaddr = getUserAddr();
String sql = "SET LOCAL application.userid='"+userid+"'; SET LOCAL application.ipaddr='"+ipaddr+"'";
em.createNativeQuery(sql).executeUpdate();
}
protected String getUserAddr() {
HttpServletRequest httprequest = CDIBeanUtils.getBean(HttpServletRequest.class);
String ipaddr = "";
if ( httprequest != null ) {
ipaddr = httprequest.getRemoteAddr();
}
return ipaddr;
}
protected String getUserId() {
String userid = "";
// Try to look up a contextual reference
if ( principal == null ) {
principal = CDIBeanUtils.getBean(Principal.class);
}
// Try to assert it from CAS authentication
if (principal == null || "anonymous".equalsIgnoreCase(principal.getName())) {
if (AssertionHolder.getAssertion() != null) {
principal = AssertionHolder.getAssertion().getPrincipal();
}
}
if ( principal != null ) {
userid = principal.getName();
}
return userid;
}
@Override
public void persist(Object entity) {
if ( em.isJoinedToTransaction() ) {
setAuditVariables();
}
em.persist(entity);
}
@Override
public T merge(T entity) {
if ( em.isJoinedToTransaction() ) {
setAuditVariables();
}
return em.merge(entity);
}
@Override
public void remove(Object entity) {
if ( em.isJoinedToTransaction() ) {
setAuditVariables();
}
em.remove(entity);
}
// Keep implementing all methods that can change
// entities so you can setAuditVariables() before
// the changes are applied.
@Override
public void createNamedQuery(.....
缺点:拦截查询(SET LOCAL)可能会在单个事务中运行多次,特别是如果在单个服务调用上有多个语句.鉴于这种情况,我们决定保持这种方式,因为它是一个简单的SET LOCAL内存调用PostgreSQL.由于没有涉及表,我们可以忍受性能损失.
现在只需在persistence.xml中替换Hibernate的持久性提供程序:
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/persistence http://xmlns.jcp.org/xml/ns/persistence/persistence_2_1.xsd"
version="2.1">
my.package.HibernatePersistenceProvider
java:app/jdbc/exemplo
作为旁注,这是CDIBeanUtils,我们必须在某些特殊场合帮助bean管理器.在这种情况下,我们使用它来查找对HttpServletRequest和Principal的引用.
public class CDIBeanUtils {
public static T getBean(Class beanClass) {
BeanManager bm = CDI.current().getBeanManager();
Iterator> ite = bm.getBeans(beanClass).iterator();
if (!ite.hasNext()) {
return null;
}
final Bean bean = (Bean) ite.next();
final CreationalContext ctx = bm.createCreationalContext(bean);
final T t = (T) bm.getReference(bean, beanClass, ctx);
return t;
}
}
公平地说,这并不是完全拦截交易事件.但是我们能够在事务中包含我们需要的自定义查询.
希望这可以帮助其他人避免我们经历的痛苦.