[seam-issues] [JBoss JIRA] (SEAMPERSIST-67) LazyInitializationException threw when persist a Many to Many collection of an entity.

[hantsy bai (Commented) (JIRA)]

    [ https://issues.jboss.org/browse/SEAMPERSIST-67?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12648668#comment-12648668 ] 

hantsy bai commented on SEAMPERSIST-67:
---------------------------------------

I have browsed the codes...you are still using the manual way to update the manytomany relation, and you do not process the "Remove" action in the multicheckboxs which is available at the edit time. Using the manual way is easy to overcome this barrier, but it is very stupid, I also used the similar solution in my project temporarily.  

If you consider this is equivalent to the Seam 2 way, you can close this issue. Of course, I do not think so.
If you think this can be improved, and Seam Team can improve it, and make it available like the Seam 2, keep this issued opened till the solution is available.

I only hope I can process the manytomany relation as Seam 2 way, no extra codes for it like the approach in my codes.
                
> 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