Hi all, We have implemented a session facade architecture, with session beans calling multiple entity beans. We have configured the <trans-attribute> as "Required" for everything, as normal.
What is the exact criteria for a session method to rollback? Is it that it must be a system initiated exception, or else the application must call setRollBackOnly()? Its just that calling this method causes a rollback, but the the container does not come up with the "Session was rolled back" exception, so I'm a bit worried about it. I know this has been addressed before on this list, so I apologise for going over old stuff, but I've noticed that some applications call the setRollbackOnly method and others don't. Is it just that those ones don't care if a rollback occurs? Specificaly, we have a stateless session bean that we invoke through a statefull one (that a servlet creates and invokes). The stateless bean always tries to create the entity beans. We would like it such that if either fails to create, the method does a rollback - all or nothing. Does this mean that we must call setRollbackOnly() ? Thanks for any help on this. Justin
