Working in a servlet, Websphere Application Server allows you to store UserTransaction objects in the HttpSession and retrieve it later, previously with a wrapper class, but now automatically:
Yet when I begin a transaction, then retrieve it later and attempt to commit, I recieve the error that no transaction exists to commit. I assume the servlet is closing the transaction automatically when the http request finishes on each servlet call - what, then, is the purpose of being able to mantain this userTransaction across sessions?
Is there any way to achieve what I want (I'm using Java with WAS)? I need some way to be able to start a transaction on the servlet, and wait for more information from the client in order to do certain statements before finally committing.