5. not quite correct - the problem is that I am waiting for a new release of Embeddable EJB3 (the most recent release was broken on Tomcat).
Are you deploying to Tomcat? If not, you can use the newer release.
Hassle the EJB3 team to do a new E-EJB3 release.
Gavin, we are still stuck with this. You also recently confirmed this http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3991260#modules/bb/templates/subSilver/images/lang_english/post.gif. I wonder, could you please advise me on where to look for the problem in the EJB area. So far I only found the http://jira.jboss.com/jira/browse/EJBTHREE-540, and also in the http://opensource.atlassian.com/projects/hibernate/browse/EJB-168.
So it is like: Hibernate team fixed it in 3.2 CR1, EJB team did so in EJB 3.0 RC7 - FD as well. But these versions are incompatible. Right?
OK, so what has to be fixed in EJB3 then? Is it http://jira.jboss.com/jira/browse/EJBTHREE-795? (Yeah, I know it says JBoss Cluster, but the linked forum topic seems to address a problem not only limited to JBoss Clustering but to Hibernate Query Cache usage.)
So, you see - I'm somewhat lost as to where I have to ask for a fix. Could you either give me a hint on the Jira issue in EJB3 context, are at least an explanation of what exactly goes wrong if a more recent EJB3 release is used?
We are nearing a production roll out, and the idea of a "could not sync"-issue on a productive systems really gives me the creeps. :-/
As usual - thanks for you support.
Did some more researching.
I think it is the "TransactionManager not bound" issue described in http://jira.jboss.com/jira/browse/EJBTHREE-771
So basically, embedded EJB is broken on Tomcat since RC9.
Seam uses RC8.
Gavin filed a problem about the RegisterSync problem (EJBTHREE-584), which was fixed in RC9.
I updated the above mentioned 771-ticket, and also cross referenced it to Gavin's 584. Hope this will get people working on this.
@Anybody who wants this fixed - I guess it´s time for some voting on 771 now.