OK. I debugged the critical code. Obviously, there are only 2 of 5 session beans registered at the NamingServer. Perhaps anybody does know, how this can happen?
OK. I now know why it doesn't work. I didn't see it until I restarted the JBoss AS instead of redeploying.
All the beans that aren't registered at the NamingServer depend on a PersistenceContext. But I didn't make any changes to these parts of my code. JBoss AS tells me that my beans are NOTYETINSTALLED since my persistence unit is NOTYETINSTALLED.
So, all I have to do is getting this connection work.
But when the AS starts up, there's following error:
Cannot obtain TransactionManager from JNDI, using TxManager.getInstance(): javax.naming.NameNotFoundException: TransactionManager not bound
Anybody encountered this error before?
There are quite a few changes in the latest release of JBoss EJB3. If you carefully look at the changes in the Seam examples between beta1 and beta2 you'll see what needs to change in your project.
Note especially that the EJB spec changed the schema for persistence.xml.
Oh. Thanks. I checked all the files, but I didn't see these little changes. After copying the Oracle-JDBC-Lib to the server's lib directory (I hate Mondays ;) it worked.