I believe I found the justification for entity beans over applications built without them. I developed a sample application that performs several database table updates within one transaction. On a rollback situation, the server just hung, I believe while the rollback was being performed. Totally unacceptable.
Will someone confirm that with entity beans, the rollback of transactions is done in the background? I can probably accomplish the same thing by putting the database updates in a separate
thread, but if it's going to get that complicated, then I might as well use entity beans.
Correction, not the server, but the application.
[ July 31, 2002: Message edited by: Elizabeth Reynolds ]