this class is part of the EJB3 spec definition (its an interface), it looks like the class is loaded at seam startup you may have to add the related jar in your classpath it won't attempt to use it if you don't have the ejb-transaction component installed in your components.xml. You definitely don't want to install this component with a tomcat installation, so just a matter of adding the EJB3 API jar in your classpath.
Thanks. I added the jar and the stacktrace disappeared.
Anyway I am getting the error of before (I didn't told you I was getting this error):
java.lang.AssertionError: javax.el.ELException: javax.persistence.PersistenceException: org.hibernate.exception.GenericJDBCException: Could not execute JDBC batch update
This happens when I flush the session, after enabling manual flushing throught
<begin-conversation join="true" flush-mode="manual"/>
I was wondering if this feature is possible with my configuration (no EJB).
Furthermore the error doesn't come out the first time I flush the entitymanager, but it starts to happen after the second.
Luckily test case is reporting the same problem.
I don't know now if this is an hibernate misconfiguration or something related to flush-mode manual.
My project (a very simple hello world) is accessible from SVN, if someone has time could give a look at http://svn2.assembla.com/svn/seam-tomcat6
Take a look at the JPA example in Seam, it deploys without any EJB API jars to Tomcat.
Also, try removing