java WFLYJPA0060：执行此操作需要事务（使用事务或扩展持久性上下文）
声明：本页面是StackOverFlow热门问题的中英对照翻译，遵循CC BY-SA 4.0协议，如果您需要使用它，必须同样遵循CC BY-SA许可，注明原文地址和作者信息，同时你必须将它归于原作者（不是我）：StackOverFlow
原文地址: http://stackoverflow.com/questions/36694311/
Warning: these are provided under cc-by-sa 4.0 license. You are free to use/share it, But you must attribute it to the original authors (not me):
StackOverFlow
WFLYJPA0060: Transaction is required to perform this operation (either use a transaction or extended persistence context)
提问by Rogério Marchiori
I losted many time try solve this issuer, but I am in the same place. I suspect that I mixed something of CDI with EJB.
我失去了很多时间尝试解决这个问题，但我在同一个地方。我怀疑我将 CDI 与 EJB 混合在一起。
The problem is persist and delete only don't work.
问题仍然存在，仅删除不起作用。
Caused by: javax.persistence.TransactionRequiredException: WFLYJPA0060: Transaction is required to perform this operation (either use a transaction or extended persistence context)
at org.jboss.as.jpa.container.AbstractEntityManager.transactionIsRequired(AbstractEntityManager.java:866)
at org.jboss.as.jpa.container.AbstractEntityManager.persist(AbstractEntityManager.java:579)
at com.oki.scope.console.model.dao.GenericDAO.save(GenericDAO.java:29)
at com.oki.scope.console.model.dao.GenericConsoleDAO.save(GenericConsoleDAO.java:12)
at com.oki.scope.console.service.ServidorServiceImp.salvar(ServidorServiceImp.java:27)
at com.oki.scope.console.service.ServidorServiceImp$Proxy$_$$_WeldClientProxy.salvar(Unknown Source)
at com.oki.scope.console.managedBean.consulta.ServidorMB.salvar(ServidorMB.java:65)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at com.sun.el.parser.AstValue.invoke(AstValue.java:292)
at com.sun.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:304)
at org.jboss.weld.util.el.ForwardingMethodExpression.invoke(ForwardingMethodExpression.java:40)
at org.jboss.weld.el.WeldMethodExpression.invoke(WeldMethodExpression.java:50)
at org.jboss.weld.util.el.ForwardingMethodExpression.invoke(ForwardingMethodExpression.java:40)
at org.jboss.weld.el.WeldMethodExpression.invoke(WeldMethodExpression.java:50)
at com.sun.faces.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:105)
at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:87)
... 40 more
My DAO
我的DAO
public class GenericDAO<T, K> {
protected EntityManager em;
private Class<T> entityClass;
public GenericDAO(Class<T> entityClass, EntityManager em) {
this.entityClass = entityClass;
this.em = em;
}
@Transactional
protected void save(T entity) {
em.persist(entity);
}
Generic DAO:
通用 DAO：
import javax.persistence.EntityManager;
public abstract class GenericConsoleDAO<T, K> extends GenericDAO<T, K> {
public GenericConsoleDAO(Class<T> entityClass, EntityManager em) {
super(entityClass, em);
}
public void save(T t){
super.save(t);
}
}
DAO Factory:
道厂：
package com.oki.scope.console.model.dao;
import java.lang.reflect.InvocationTargetException;
import java.util.Collections;
import java.util.HashMap;
import java.util.Map;
import javax.ejb.Singleton;
import javax.ejb.TransactionManagement;
import javax.ejb.TransactionManagementType;
import javax.enterprise.inject.Produces;
import javax.persistence.EntityManager;
import javax.persistence.PersistenceContext;
@Singleton
@TransactionManagement(TransactionManagementType.CONTAINER)
public class DAOConsoleFactory {
private final static String UNIT_NAME = "scope-console";
private static Map<String, Object> mapa = Collections.synchronizedMap(new HashMap<String, Object>());
@PersistenceContext(unitName = UNIT_NAME )
private EntityManager entityManager;
@Produces public ServidorDAO criaServidorDAO(){ return getDAO(ServidorDAO.class); }
@Produces public ConexaobdDAO criaConexaoDAO(){ return getDAO(ConexaobdDAO.class); }
@Produces public ContratoDAO criaContratoDAO(){ return getDAO(ContratoDAO.class); }
@Produces public EmpresaDAO criaEmpresaDAO(){ return getDAO(EmpresaDAO.class); }
@Produces public LojaDAO criaLojaDAO(){ return getDAO(LojaDAO.class); }
//@Produces public RedeAutorizadoraDAO criaRedeAutorizadoraDAO(){ return getDAO(RedeAutorizadoraDAO.class); }
@Produces public RedeDAO criaRedeDAO(){ return getDAO(RedeDAO.class); }
@Produces public RoteadorDAO criaRoteadorDAO(){ return getDAO(RoteadorDAO.class); }
@Produces public TerminalDAO criaTerminalDAO(){ return getDAO(TerminalDAO.class); }
@Produces public TipoHeaderDAO criaTipoHeaderDAO(){ return getDAO(TipoHeaderDAO.class); }
@SuppressWarnings("unchecked")
public <E> E getDAO(Class<E> classe){
String key = classe.getSimpleName();
if (!mapa.containsKey(key))
{
try {
mapa.put(key, classe.getDeclaredConstructor(EntityManager.class).newInstance(entityManager));
} catch (InstantiationException | IllegalAccessException | IllegalArgumentException
| InvocationTargetException | NoSuchMethodException | SecurityException e) {
System.out.println("Classe "+ key +" n?o possui um construtor que tenha EntityManager como parametro.");
}
}
return (E)mapa.get(key);
}
}
My class:
我的课：
@Named
@ApplicationScoped
public class ServidorServiceImp implements ServidorService {
@Inject private ServidorDAO dao;
@Override
public List<Servidor> getLista() {
return dao.getLista();
}
@Override
public void salvar(Servidor servidor) {
if (servidor.getId()==0){
dao.save(servidor);
}
else
{
dao.update(servidor);
}
}
@Override
public void remover(Servidor servidor) {
dao.delete(servidor);
}
}
回答by K.Nicholas
In trying to enhance performance, you have circumvented what the container is supposed to be doing for you, which is instantiating a bean inside a transaction.
在尝试提高性能时，您绕过了容器应该为您做的事情，即在事务中实例化一个 bean。
I would say remove the @Singletonand @TransactionManagement(TransactionManagementType.CONTAINER)from DAOConsoleFactoryand allow the EJB transaction to be handled by the EJB bean that's using the DAO's.
我会说删除@Singletonand @TransactionManagement(TransactionManagementType.CONTAINER)fromDAOConsoleFactory并允许 EJB 事务由使用 DAO 的 EJB bean 处理。
UPDATE: Also, @ApplicationScopedis not an EJB annotation Class ServidorServiceImpneeds to be an EJB bean so, it should be annotated with @Statelessor perhaps @Statefulland remove the @ApplicationScoped. It reads like a stateless EJB bean, so there is no need to make it application scoped.
更新：此外，@ApplicationScoped不是 EJB 注释类ServidorServiceImp需要是 EJB bean，因此，它应该使用@Stateless或可能@Statefull并删除@ApplicationScoped. 它读起来像一个无状态的 EJB bean，所以没有必要使它成为应用程序范围的。
Again, it seems to me you are concentrating too much on trying to optimize performance without having a good understanding of how EJB's are supposed to work in a container. I would recommend getting everything to work and follow architectural best practices, especially in the "Session Fa?ade" concept. Some of these posts may help: What is the point of a Facade in Java EE?or Why use Facade pattern for EJB session bean.
同样，在我看来，您过于专注于尝试优化性能，而没有很好地了解 EJB 应该如何在容器中工作。我建议让一切正常工作并遵循架构最佳实践，尤其是在“Session Fa?ade”概念中。其中一些帖子可能会有所帮助：Java EE 中的 Facade 有何意义？或者为什么对 EJB 会话 bean 使用 Facade 模式。
回答by Rogério Marchiori
Solved: Before 2 day suffering. The problem was in my Class. Where is @Named @ApplicationScoped, I changed to @Statefull.
解决：前2天的痛苦。问题出在我的班级。@Named @ApplicationScoped 在哪里，我改成了@Statefull。
