|
I posted a message earlier that referring to data being
committed on Tengah even though the transaction was rolled back.
After further investigation, I have figured out what the issue
was. I was doing an example in a book I have that was opening a DB connection
during the ejbCreate() method, and then on the business method calls, was using
the connection to make updates. Although I think this is wasteful (holding a
connection too long), I didn't see anything in the Spec that said that it was
not legal. However if you do this with a Tengah Server, the transactions always
get commited, regardless of the transaction results.
When I moved the connection open/close code to each business
method, it worked. This is probably the most appropriate way to manage things,
but I am curious if this is a Tengah bug, or is it actually illegal to hold
connections in a STATEFUL session bean?
Thanks.
--Chris.
|
