[
https://issues.jboss.org/browse/SEAMPERSIST-67?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12771584#comment-12771584
]
Ben Software Engineer commented on SEAMPERSIST-67:
--------------------------------------------------
Thanks Hantsy for the thoughts. We have a forms heavy highly customizable SaaS
product that we find JSF very well suited for. I also think facelets is the
best templating engine in then industry. EL expressions can be great for
business rules that integrate into system easily. It's the rest I have issues
with. Ajax is slow and does too much. Richfaces regions to solve this problem
do not seem to work well. Transaction mgmt and scope/context issues are way to
complex. They create problems larger than the ones they solve (flipping an
auto commit flag off and having a managed map of named beans). I am really
disappointed in the cross integration of lazy fetch in ORM/hibernate. It seams
the design and idea is not even supported well without extra magic. JSF
validation can be such a pain, just try to implement a "reset button" or do a
"save for later" mechanism to let user save partial form without validation yet.
As for Seam, it has the difficult combination of innovating around java spec
limits but also influencing them, thereby guaranteeing migration issues in the
future to standards. It also is way too invasive. We found only way out of
Seam was to upgrade first so we can iteratively move to standard JSF 2 stuff.
> 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
_______________________________________________
seam-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/seam-issues
