Hi,

the CaveatEmptor app (v0.9.5) uses a servlet filter in order to demarcate transaction boundaries (HibernateUtil.commitTransaction()). As far as I understand the j2ee spec, this is not allowed in case of JTA.

j2ee spec [1] says: "Servlet filters and web application event listners must not demarcate transactions using the javax.transaction.UserTransaction interface. Servlet filters may use transactional resources in a local transaction mode within their doFilter methods but should not use any transactional resources in the methods of any object used to wrap the request or response object."

Do I misunderstand something?!




[1] J2EE specification 1.4, chapter 4.2.1, pp. 47 (and J2EE 1.3 as well)

You are correct. However, this does work on all platforms ;-)

What about using a filter only to create and close the session and creating a transaction in a base struts action?

This would:

Have the session available for filling in lazy data for the jsp page

Have the transaction commited or not in the business layer

Not violate the spec?