Hello Forum,

I would be grateful to hear from experienced people what is the correct approach is this case.

The standard situation that I have is following(for example):

I have two hibernate beans:




I'm going to show Person information edit dialog which contains the list of by user spoken languages.

Struts:



JSP:



If I do this I'm getting IllegalStateException ot something like that - because the hibernateSession is closed.
So either I have to use some other instance(not those one that I get using "find"), something like

...


or I can put all the attributes(Set<Language> as well) in ActionForm that I use in Struts action and use it on JSP instead of http session attribute.

I found the example of struts and hibernate integration: http://www.laliluna.de/struts-hibernate ... al-en.html

They have always one session object and they don't close it at all. So I have an abstract Action extended from all the others and doing following:



or I save it in httpSession and have hibernateSession per httpSession.

But in both cases hibernateSession stays not closed!

What does that mean and what is the correct approach?

I hope I wxplained all not very complicated way.

Many thanks in advance.

Try this before closing the Session

session.save(object);

Hi,

thanks for your answer.

I can do it, of course, but why? I'm performing no changes. What should I save?

The thing is that the application is working properly (now, as it's un develoopment), but what happens when many users are working with it?

Regards,

Giorgi

I suggest you to take a serious look at OpenSessionInView pattern:

http://www.hibernate.org/43.html

The reading of this could seem a bit complicated for a newbie (as I am), but I can state (on my experience) that it clearify a lot of dark corners in web application development.

In short terms: open Hibernate Session in Struts Action (or before, with a http filter) and keep it open until the end of view rendering.
A better implementation, as stated in this page, is the use of two connections: one for the action (read/write for application logic) and another for the rendering of the view.

Take a look also at "Long conversation":

http://www.hibernate.org/hib_docs/v3/re ... sics-apptx

Hi,

thanks for you answer and sorry for late reaction :-)

That's a very interesting article - have never come accross to it.

If I understand correctly the session for View stays opened until the "real" action comes and does commit and close...

The good thing is that probably I don't have to rebuild my solutions as I have two abstract struts actions: with session close(used for updates) and without session close(for views - such as start editing...).

Anyway, thank you for that link.