Sorry to bump but this is really important. Someone of the Seam team ?
I am using Seam 2.0 and JBoss 4.2.2
Thanks
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4111657#4111657
Reply to the post :
This isn't a Seam issue, it's a Tomcat/environment issue. Googling on this
particular exception with Tomcat returns a multitude of results, although
nothing concrete that I can point you to, sorry.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4111683#4111683
