tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lance (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (TAP5-2115) Document how the hibernate session is implemented
Date Mon, 13 May 2013 08:43:16 GMT

     [ https://issues.apache.org/jira/browse/TAP5-2115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Lance updated TAP5-2115:
------------------------

    Summary: Document how the hibernate session is implemented  (was: tapestry-hibernate documentation:
Description of how the session is managed)
    
> Document how the hibernate session is implemented
> -------------------------------------------------
>
>                 Key: TAP5-2115
>                 URL: https://issues.apache.org/jira/browse/TAP5-2115
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: documentation, tapestry-hibernate
>            Reporter: Lance
>            Priority: Minor
>              Labels: documentation, hibernate
>
> There have been many questions on the user's list about how the hibernate session is
implemented in tapestry-hibernate and also how to use tapestry-hibernate outside of a tapestry
managed request / response.
> I think that the documentation should mention the following:
> 1. The hibernate session service provided by tapestry-hibernate is a singleton
> 2. The singleton is a proxy that points to a per-thread, lazy loaded hibernate session
instance
> 3. The per-thread session instance is cleaned up by Registry.cleanupThread() /
> PerThreadManager.cleanup()
> 4. Tapestry automatically cleans up the thread local inside the normal request / response
flow
> 5. Outside of a tapestry managed request / response, you must explicitly cleanup the
thread

--
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

Mime
View raw message