[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-991) Make seam managed PC replacement for Spring OpenXXXInView

Michael Youngstrom (JIRA) jira-events at lists.jboss.org
Fri Mar 30 11:26:19 EDT 2007

    [ http://jira.jboss.com/jira/browse/JBSEAM-991?page=comments#action_12357937 ] 
Michael Youngstrom commented on JBSEAM-991:

Well, what I have committed so far applies only to JPA however.  I was planning to do a Hibernate version as well once the general concept for JPA was validated however it appears I may have to add Hibernate support sooner then I wanted to.

When I do a Hibernate version of the integration it would be used in theory the same way you are currently using Spring+Hibernate.  You would remove the OpenSessionInViewFilter, create a SeamManagedSessionFactoryBean and you should be able to use session.getCurrentSession() just like you are currently using assuming you have spring set up correctly to return the current spring configured session from getCurrentSession().  But, if you put seam in front of it then you will be able to begin a long running conversation and have access to that extended persistence context across requests instead of having to create a new Session every request.

How about this, I'll do some looking into a Hibernate version of the integration if you will try it out before the 1.3.0 beta release. :)  How does that sound?


> Make seam managed PC replacement for Spring OpenXXXInView
> ---------------------------------------------------------
>                 Key: JBSEAM-991
>                 URL: http://jira.jboss.com/jira/browse/JBSEAM-991
>             Project: JBoss Seam
>          Issue Type: Feature Request
>          Components: Spring
>    Affects Versions: 1.2.0.GA
>            Reporter: Michael Youngstrom
>         Assigned To: Michael Youngstrom
>             Fix For: 1.3.0.BETA1
> True seam hibernate and JPA integration would be to replace the Spring OpenEntityManagerInView and OpenSessionInView filters with a Seam managed Persistence Context.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the seam-issues mailing list