Spring would be a good way to manage this. It uses aspect oriented programming techniques to manage transactions. Usually they're added to POJO service interfaces.
You can choose to expose your POJO services using RMI, but that's just one choice among many.
Spring would be a good way to manage this. It uses aspect oriented programming techniques to manage transactions. Usually they're added to POJO service interfaces.
You can choose to expose your POJO services using RMI, but that's just one choice among many. I wouldn't associate a transaction with a session unless it was very long running. Another approach would be to embrace EJB 3.0.It took a lot from Spring: dependency injection, aspect oriented programming.
It also has a declarative transaction model.
Thanks, I'll give Spring a go. It seemed like the right way to go but with limited Java knowledge I wasn't sure :) – James Antrobus Dec 7 '10 at 22:55.
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.