Why would you put a reference to the application in your session
anyway? You can get the current app like Application.get(). Otherwise,
you can make the field transient, though when it gets deserialized,
you'd have to set the field yourself somehow.
Eelco
On 12/4/06, Ingram Chen [EMAIL
hhmm as Wicket always check serializable, I think my app's session does
not refererence to non-serializable WebApplication. but the stack trace
shows:
com.tc.object.ClientObjectManagerImpl.lookupOrCreate(ClientObjectManagerImpl.java:306)
is the option that transient fields must be left alone (not serialized) on
by default?
johan
On 12/5/06, Ingram Chen [EMAIL PROTECTED] wrote:
hhmm as Wicket always check serializable, I think my app's session
does not refererence to non-serializable WebApplication. but the stack
trace
But this just seems a bug.
Can you add an issue to jira for this?
johan
On 12/5/06, Ingram Chen [EMAIL PROTECTED] wrote:
Thanks for the tips, I turn on Honor transient and finally my webapp
startup successfully.
after playing some pages and I switch from one server to another
server. I
I just test terracotta-session, but it report error:
com.tc.exception.TCNonPortableObjectError:
***
Attempt to share an instance of a non-portable class referenced by a
portable class. This
unshareable class is a
