- Seam-gen ejb version does not really generate EJB code
- JNDI naming conventions for GLASSFISH does not follow that of Jboss. Each ejb has to be mentioned at-lease twice in the web.xml
- Seam proposes that the injection of Entitymanger should be left to Seam. One of the argument is that seam has better transaction management which is compatible with Seam conversations.
- This requires that we enable Seam Managed Transactions
- Consequence is EjbSynchronizations provided by Seam has to be deployed
Seam provides power full features for Enterprise development. There are few startup issues while working in non-jboss servers. Give the benefits of seam the limitations are negligible.
Note : For detailed discussion on how to address the above issues refer to my previous blog Kooking Seam with Glassfish