When using OpenSessionInView; calling "myEntitiy. SetSomething(...)" will only change the value within that session. You must still persist the object when you want it be to stored for later use.
When using OpenSessionInView; calling "myEntitiy. SetSomething(...)" will only change the value within that session. You must still persist the object when you want it be to stored for later use.
I prefer creating a "buisiness layer" where transactions start and within that business layer handle all jpa operations. That is, every business method is within its own transaction and provides a specified service for the gui layer above.
I would strongly suggest you to see Seam, you can find it here. One of the biggest reasons why I switch to seam was this.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.