[
http://opensource.atlassian.com/projects/hibernate/browse/EJB-267?page=all ]
Emmanuel Bernard resolved EJB-267:
----------------------------------
Resolution: Fixed
Actually I was wrong, this feature is present and tested since 3.2.0.CR2
Are you sure you have HAN 3.2.1 running? (not the default in JBoss EJB 3).
If you are sure, this is a bug in JBoss EJB3
FlushMode.MANUAL being ignored???
---------------------------------
Key: EJB-267
URL:
http://opensource.atlassian.com/projects/hibernate/browse/EJB-267
Project: Hibernate Entity Manager
Type: Task
Components: EntityManager
Versions: 3.2.2
Environment: Hibernate Entity Manager 3.2.1.GA
Reporter: James Woodward
The following code is advocated as best practice in the book "Java Persistence with
Hibernate" for creating an extended persistence context in a SFSB, but the
persistence property is currently being ignored.
@PersistenceContext(type=PersistenceContextType.EXTENDED,
properties=(a)PersistenceProperty(name="org.hibernate.flushMode",
value="MANUAL"))
private EntityManager entityManager;
As a workaround you can set the flushMode in a business method using the following code:
public void init() {
org.hibernate.Session session = ((org.jboss.ejb3.entity.HibernateSession)
entityManager).getHibernateSession();
session.setFlushMode(org.hibernate.FlushMode.MANUAL);
}
See
http://forum.hibernate.org/viewtopic.php?t=970727 for details.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira