according to the j2ee spec, afair, httpsession must not hold any
non-serializable objects.
-igor
On Tue, Oct 28, 2008 at 10:02 AM, eyalbenamram [EMAIL PROTECTED] wrote:
Hi,
My session is holding an non serializable object. this causes a problem
every time wicket is trying to serialize a page
Thank you for the quick response.
eyalbenamram wrote:
Hi,
My session is holding an non serializable object. this causes a problem
every time wicket is trying to serialize a page (since most pages in my
app are hoding a pointer to the session) Here is the exception:
http-6789-6 ERROR
The problem is, this object the session is holding cannot be serialized. Is
there a way
to hold this object on a defferent level or detach it from the session
despite the J2ee specs?
igor.vaynberg wrote:
according to the j2ee spec, afair, httpsession must not hold any
non-serializable
what is its scope? what is the object?
-igor
On Tue, Oct 28, 2008 at 11:09 AM, eyalbenamram [EMAIL PROTECTED] wrote:
The problem is, this object the session is holding cannot be serialized. Is
there a way
to hold this object on a defferent level or detach it from the session
despite the
the object negotiates between the user and a server that provides a messaging
service.
there is a new object for each user - thus it must sit in the session.
The object contains non serializable objects such as sockets and
httpRequests...
igor.vaynberg wrote:
what is its scope? what is the
you can keep those in your application object, or servlet-context if
you think in j2ee terms.
so application.mapsessionid,object and when the session is destroyed
you remove it from the map.
-igor
On Tue, Oct 28, 2008 at 11:32 AM, eyalbenamram [EMAIL PROTECTED] wrote:
the object negotiates
