Folks, what's the difference between Open Session in View and Session per request pattern? I am using Spring MVC and Hibernate . I am not talking about the transaction demarcation here, for Session per request seems to be 1 session:1 tx. But for OSIV, there is 1 session and then there are multiple transactions(1 for each service call). Can someone please shed some light on this?
Difference between session per request and Open Sesson in view pattern
2k Views Asked by Achow At
1
There are 1 best solutions below
Related Questions in OPEN-SESSION-IN-VIEW
- Display images on Django Template Site
- Protractor did not run properly when using browser.wait, msg: "Wait timed out after XXXms"
- Django invalid literal for int() with base 10:
- Removing URL features from tokens in NLTK
- Django Noob URL to from Root Page to sub Page
- Django Admin tables not displaying correctly
- Django with chartkick
- Django urls.py not rendering correct template
- django form errors before submit
- django admin: custom app_index with context
Related Questions in SESSION-PER-REQUEST
- Display images on Django Template Site
- Protractor did not run properly when using browser.wait, msg: "Wait timed out after XXXms"
- Django invalid literal for int() with base 10:
- Removing URL features from tokens in NLTK
- Django Noob URL to from Root Page to sub Page
- Django Admin tables not displaying correctly
- Django with chartkick
- Django urls.py not rendering correct template
- django form errors before submit
- django admin: custom app_index with context
Trending Questions
- UIImageView Frame Doesn't Reflect Constraints
- Is it possible to use adb commands to click on a view by finding its ID?
- How to create a new web character symbol recognizable by html/javascript?
- Why isn't my CSS3 animation smooth in Google Chrome (but very smooth on other browsers)?
- Heap Gives Page Fault
- Connect ffmpeg to Visual Studio 2008
- Both Object- and ValueAnimator jumps when Duration is set above API LvL 24
- How to avoid default initialization of objects in std::vector?
- second argument of the command line arguments in a format other than char** argv or char* argv[]
- How to improve efficiency of algorithm which generates next lexicographic permutation?
- Navigating to the another actvity app getting crash in android
- How to read the particular message format in android and store in sqlite database?
- Resetting inventory status after order is cancelled
- Efficiently compute powers of X in SSE/AVX
- Insert into an external database using ajax and php : POST 500 (Internal Server Error)
Popular # Hahtags
Popular Questions
- How do I undo the most recent local commits in Git?
- How can I remove a specific item from an array in JavaScript?
- How do I delete a Git branch locally and remotely?
- Find all files containing a specific text (string) on Linux?
- How do I revert a Git repository to a previous commit?
- How do I create an HTML button that acts like a link?
- How do I check out a remote Git branch?
- How do I force "git pull" to overwrite local files?
- How do I list all files of a directory?
- How to check whether a string contains a substring in JavaScript?
- How do I redirect to another webpage?
- How can I iterate over rows in a Pandas DataFrame?
- How do I convert a String to an int in Java?
- Does Python have a string 'contains' substring method?
- How do I check if a string contains a specific word?
The definining characteristic of OSIV isn't really the multiple transactions, but rather that the session remains open while the view is being rendered. This page on the JBoss wiki illustrates this setup (though managing transactions manually from the web layer is not my cup of tea... for something more pre-packaged, see Spring's OpenSessionInViewFilter).
There is one session, one transaction. This is stil OSIV, because all the work, including rendering the view is done inside the scope of the session. Note that even if you mark all your service methods as @Transactional (or the XML equivalent), they will still participate in the same single transaction unless they specifically require a new transaction to be started.
So OSIV can be a type of session-per-request, and they are sometimes used interchangeably. But I would say that it is possible to have a session per request implementation that is not OSIV, if you make sure to close your single session prior to view rendering.