Yes, definitely we want to support EJB 3.1 - I know glassfish has an implementation of the EDR. Care to give it a spin?
I'm not sure what module framework is. Can you enlighten us?
Of course, glassfish has an implementation - why don't you give Seam a spin on it? Report issues in JIRA.
Seam runs very nicely on Glassfish v2; with jsf1.2_8, facelets, richfaces, svg, etc. I attached a crib sheet to http://forums.java.net/jive/thread.jspa?messageID=277713񃳑 about running Seam in v2.
Glassfish v3 is ejb 3.1 based and is also a different architecture. A v2 war+ejb+ear 3 projects style has been altered so now the ejb 3.1 can be in a 3.1 style war only; a single project. To better understand, these links are more helpful than me resaying a bunch of it.
Seam with 3.0 ejb architecture hasn't run on Glassfish v3 for me but the gf ejb 3.1 implementation runs stateless beans very well. I haven't tried the new features such as timers and asynchronous invocation but converted ejb 3.0's ran readily. The project simplification and v3 standing up in a few seconds is a big boost. Although redeploys aren't working, I can delete a webapp, restart v3 and deploy faster than the test cycles with v2; especially where the PermGen out-of-memory error happens.
Now I see in the above article part 4 the mention of Web Beans (Seam architect Gavin King) and Guice( Bob Lee) putting together some excellent technology for ejb 3.1. Anxious to test with it:-)
The architecture of glassfish v3 is a major change from v2.
which is based on Module subsystems of hk2 (https://hk2.dev.java.net/) Although I don't know if Seam would need to be or fit into a v3 module or would only need to be in a developers 3.1 style war project.
Seam isn't built to run in a module style system, however Web Beans probably will be a better fit for this.