all container call backs are invoked in unspecified transaction?
yamini nadella
Ranch Hand
Posts: 257
posted 12 years ago
does all container call backs of all bean types are invoked in un specified transaction context?
SessionSynchronization.afterCompletion() is invoked in no transaction.
is no transaction and unspecified transactions are same?.
can we use setRollbackOnly() on unspecified transactions?
Thanks,
Yamini.
SessionSynchronization.afterCompletion() is invoked in no transaction.
is no transaction and unspecified transactions are same?.
can we use setRollbackOnly() on unspecified transactions?
Thanks,
Yamini.
Paulus Maessen
Greenhorn
Posts: 12
posted 12 years ago
Hi Yamini,
if you haven't obtained a copy of the EJB specification from SUN you should because you can find it there:
1. Not all. The specification lists the callbacks that run in an unspecified transaction context.
2. Unspecified transaction context means that the specification doesn't demand anything from the container. Some containers may use a transaction, others may use no transaction at all.
3. No. See e.g. table in par. 7.6.1. I believe the container will throw a java.lang.IllegalStateException.
Hope this helps,
Paulus
if you haven't obtained a copy of the EJB specification from SUN you should because you can find it there:
1. Not all. The specification lists the callbacks that run in an unspecified transaction context.
2. Unspecified transaction context means that the specification doesn't demand anything from the container. Some containers may use a transaction, others may use no transaction at all.
3. No. See e.g. table in par. 7.6.1. I believe the container will throw a java.lang.IllegalStateException.
Hope this helps,
Paulus
