There is something I forgot to tell you: WebSessionContext is NOT serializable.
So if you have injected it into your SFSB, and the SFSB gets passivated (i.e.
serialized) after some idle time, the sessionContext gets lost. And when
reactivating the SFSB and accessing sessionContext you will get:
Right, this should be mentioned in the Seam docs.
Perhaps we should even make Seam warn about it...
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3962917#3962917
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3962917
First: You don't need to write value=sessionContext since the name of the
annotated variable is the same, namely sessionContext. You only need to
explicitely set the value when the variable's name ist different from the seam
component name.
Ok, now to your problem: The last Exception says that
Stop, forget what I said. I just had a look at
UnsafeObjectFieldAccessorImpl.java and its set-method:
public void set(Object obj, Object value)
| throws IllegalArgumentException, IllegalAccessException
| {
| ensureObj(obj);
| if (isFinal) {
|
Righto. Because SessionContext is probably package access only and I must use
the Context Interface. I'll give it a shot.
Thanks for the help.
Eric
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3962502#3962502
Reply to the post :
