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

hantsy bai (JIRA) jira-events at lists.jboss.org
Thu May 2 01:19:53 EDT 2013


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

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

Oh, my God, this discussion was posted 1.5 year ago.

I think the collectionType is not the only problem.

A big problem is the converter.

I have read the codes of Seam 2 entityConverter, for the MultiSelectCheckBox/MultiList, it will convert between List<PK> and List<Entity TYPE>(and other types, such as Collection, Set, array).

But the object converter in Seam 3 does not provides such a features.

In fact, in the last two years, I have spent much time on JSF2/Richfaces4/Seam3 in projects, and some problems still can not be resolved.

Personally, I had got every bad experience when use Richfaces 4 and Seam 3. And later, I gave up Richfaces 4 rich components, and used pure JSF+ Richfaces A4j+ Twitter Boostrap + Seam3.

Now I am trying to give up JSF in new website based application, and use REST(backend)+JS/AngularJS(frontend) . I think in future I will use JSF in internal app or backend admin for some application.



Hantsy





                
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the seam-issues mailing list