Just wondering if anyone else is concerned with packaging so many Seam JARs into each web-app?
In our Struts applications the JARs are also packaged with the application and we've had trouble convincing people to upgrade their libraries to stay current.
On the other hand we've upgraded the application server multiple times and never had much trouble getting people to test/update apps for newer libraries packaged with the app server.
It seems easier if I can deploy a single version of Seam to match the app server and keep them in step.
Seam is designed to be local to each application. While I think making it work in a shared-JAR environment would be a nice thing, you won't be able to make it work with Seam as it exists now.