[
https://issues.jboss.org/browse/SEAMPERSIST-67?page=com.atlassian.jira.pl...
]
hantsy bai edited comment on SEAMPERSIST-67 at 12/1/11 2:32 AM:
----------------------------------------------------------------
There is another problem you must know...in the four cases, I used @Transacational or
em.flush...
I have removed the following in the persistence.xml.
<property name="hibernate.transaction.flush_before_completion"
value="true" />
Without em.flush(creat1, create2), even there is a @Transacational on method, the data
will not be saved.
Maybe I could create another issue about this?
was (Author: hantsy):
There is another problem you must know...in the four cases, I used @Transacational or
em.flush...
I have removed the following in the persistence.xml.
<property name="hibernate.transaction.flush_before_completion"
value="true" />
With em.flush, even there is a @Transacational on method, the data will not be saved.
Maybe I could create another issue about this?
LazyInitializationException threw when persist a Many to Many
collection of an entity.
--------------------------------------------------------------------------------------
Key: SEAMPERSIST-67
URL:
https://issues.jboss.org/browse/SEAMPERSIST-67
Project: Seam Persistence
Issue Type: Bug
Environment: Java 6 update 27, Seam 3.1.0Beta2, JBoss 7.0.1.Final
Reporter: hantsy bai
Priority: Critical
I tried a saved a many to many relation(multicheckbox), but failed.
But in before seam 2 application, I used like this, never encounter such a problem.
I used Seam managed Persistence, and added TransactionIntercepter in the beans.xml.
Please refer the discussion in the forum.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira