[
https://issues.jboss.org/browse/SEAMPERSIST-67?page=com.atlassian.jira.pl...
]
hantsy bai edited comment on SEAMPERSIST-67 at 12/7/11 7:38 PM:
----------------------------------------------------------------
In my project, I only copied the codes from Seam 2 version to the current application(I am
helping the customer to migrate a seam 2 application to Seam3/JEE6). In the seam2
version(jsf1.2, JPA1/Hibernate 3.3, Seam 2.2), it worked well, the relation was set
correctly automatically.
was (Author: hantsy):
In my project, I only copied the codes from Seam 2 version to the current
application(I am helping the customer to migrate a seam 2 application to Seam3/JEE6). In
the seam2 version(jsf1.2, Seam 2.2), it worked well, the relation was set correctly
aumatically.
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