Ah yes - this was down to a mix in jboss-serialization.jar versions.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3989507#3989507
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3989507
Yeah, I'd read that in the release notes and with a fix for JBSEAM-325 these
were my main driver for upgrading to 1.1. So I am actually using Seam 1.1 CR1
now and the exception reported in my original post was for the following bean:
@Stateful
| @Scope(SESSION)
| @Name(changePassword)
|
Looks like a classloading problem to me, not a serializability problem.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3988457#3988457
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3988457
You don't need to check serializability of @In fields, since they are nullified
by Seam (1.1) at the end of the invocation.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3988286#3988286
Reply to the post :
