I have seen this exception, but in my case is was always due to an error on my part and
disappeared after I fixed it.
I am currently using Seam 1.2.1 on JBAS 4.2.1 in production.
I will switch to Seam 2.0 as soon as it comes out though.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4070899#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...