Re: Serialization problem - detaching an oblect from session

2008-10-28 Thread Igor Vaynberg
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 (since most pages in my app
 are hoding a pointer to the session) Here is the exception:

 http-6789-6 ERROR lang.Objects - Error serializing object class
 screens.Login [object=[Page class = screens.Login, id = 4, version = 0]]
 org.apache.wicket.util.io.SerializableChecker$WicketNotSerializableException:
 Unable to serialize class: java.lang.Object
 Field hierarchy is:
  4 [class=screens.Login, path=4]
MySession screens.Login.ns [class=MySession]
  private _community [class=core.community.User]
public core.community.TransactionManager
 core.community.User.transactionManager
 [class=core.community.TransactionManager]
  private core.transportLayer.Protocol
 core.community.TransactionManager.protocol
 [class=core.transportLayer.Protocol]
private network.NetworkManger
 core.transportLayer.Protocol.network [class=network.NetworkManger]
  private java.util.Hashtable network.NetworkManger.poolManagers
 [class=java.util.Hashtable]
private java.util.Hashtable
 network.NetworkManger.poolManagers[write:1][write:2]
 [class=network.PoolManager]
  private java.util.Vector
 network.PoolManager.availableTransports [class=java.util.Vector]
private java.util.Vector
 network.PoolManager.availableTransports[write:1] [class=[Ljava.lang.Object;]
  private java.util.Vector
 network.PoolManager.availableTransports[write:1][0]
 [class=network.Transport]
private java.lang.Object
 network.Transport.messageProcessingLock [class=java.lang.Object] -
 field that is not serializable

 Is it possible that this object (held by the session) will not be serialized
 at all??

 Thanks, Eyal.
 --
 View this message in context: 
 http://www.nabble.com/Serialization-problem---detaching-an-oblect-from-session-tp20211477p20211477.html
 Sent from the Wicket - User mailing list archive at Nabble.com.


 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Serialization problem - detaching an oblect from session

2008-10-28 Thread eyalbenamram

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 lang.Objects - Error serializing object class
 screens.Login [object=[Page class = screens.Login, id = 4, version = 0]]
 org.apache.wicket.util.io.SerializableChecker$WicketNotSerializableException:
 Unable to serialize class: java.lang.Object
 Field hierarchy is:
   4 [class=screens.Login, path=4]
 MySession screens.Login.ns [class=MySession]
   private _community [class=core.community.User]
 public core.community.TransactionManager
 core.community.User.transactionManager
 [class=core.community.TransactionManager]
   private core.transportLayer.Protocol
 core.community.TransactionManager.protocol
 [class=core.transportLayer.Protocol]
 private network.NetworkManger
 core.transportLayer.Protocol.network [class=network.NetworkManger]
   private java.util.Hashtable
 network.NetworkManger.poolManagers [class=java.util.Hashtable]
 private java.util.Hashtable
 network.NetworkManger.poolManagers[write:1][write:2]
 [class=network.PoolManager]
   private java.util.Vector
 network.PoolManager.availableTransports [class=java.util.Vector]
 private java.util.Vector
 network.PoolManager.availableTransports[write:1]
 [class=[Ljava.lang.Object;]
   private java.util.Vector
 network.PoolManager.availableTransports[write:1][0]
 [class=network.Transport]
 private java.lang.Object
 network.Transport.messageProcessingLock [class=java.lang.Object] -
 field that is not serializable
 
 Is it possible that this object (held by the session) will not be
 serialized at all??
 
 Thanks, Eyal.
 

-- 
View this message in context: 
http://www.nabble.com/Serialization-problem---detaching-an-oblect-from-session-tp20211477p20211817.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Serialization problem - detaching an oblect from session

2008-10-28 Thread eyalbenamram

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 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 (since most pages in my
 app
 are hoding a pointer to the session) Here is the exception:

 http-6789-6 ERROR lang.Objects - Error serializing object class
 screens.Login [object=[Page class = screens.Login, id = 4, version = 0]]
 org.apache.wicket.util.io.SerializableChecker$WicketNotSerializableException:
 Unable to serialize class: java.lang.Object
 Field hierarchy is:
  4 [class=screens.Login, path=4]
MySession screens.Login.ns [class=MySession]
  private _community [class=core.community.User]
public core.community.TransactionManager
 core.community.User.transactionManager
 [class=core.community.TransactionManager]
  private core.transportLayer.Protocol
 core.community.TransactionManager.protocol
 [class=core.transportLayer.Protocol]
private network.NetworkManger
 core.transportLayer.Protocol.network [class=network.NetworkManger]
  private java.util.Hashtable
 network.NetworkManger.poolManagers
 [class=java.util.Hashtable]
private java.util.Hashtable
 network.NetworkManger.poolManagers[write:1][write:2]
 [class=network.PoolManager]
  private java.util.Vector
 network.PoolManager.availableTransports [class=java.util.Vector]
private java.util.Vector
 network.PoolManager.availableTransports[write:1]
 [class=[Ljava.lang.Object;]
  private java.util.Vector
 network.PoolManager.availableTransports[write:1][0]
 [class=network.Transport]
private java.lang.Object
 network.Transport.messageProcessingLock [class=java.lang.Object] -
 field that is not serializable

 Is it possible that this object (held by the session) will not be
 serialized
 at all??

 Thanks, Eyal.
 --
 View this message in context:
 http://www.nabble.com/Serialization-problem---detaching-an-oblect-from-session-tp20211477p20211477.html
 Sent from the Wicket - User mailing list archive at Nabble.com.


 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]


 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 

-- 
View this message in context: 
http://www.nabble.com/Serialization-problem---detaching-an-oblect-from-session-tp20211477p20212873.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Serialization problem - detaching an oblect from session

2008-10-28 Thread Igor Vaynberg
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 J2ee specs?


 igor.vaynberg wrote:

 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 (since most pages in my
 app
 are hoding a pointer to the session) Here is the exception:

 http-6789-6 ERROR lang.Objects - Error serializing object class
 screens.Login [object=[Page class = screens.Login, id = 4, version = 0]]
 org.apache.wicket.util.io.SerializableChecker$WicketNotSerializableException:
 Unable to serialize class: java.lang.Object
 Field hierarchy is:
  4 [class=screens.Login, path=4]
MySession screens.Login.ns [class=MySession]
  private _community [class=core.community.User]
public core.community.TransactionManager
 core.community.User.transactionManager
 [class=core.community.TransactionManager]
  private core.transportLayer.Protocol
 core.community.TransactionManager.protocol
 [class=core.transportLayer.Protocol]
private network.NetworkManger
 core.transportLayer.Protocol.network [class=network.NetworkManger]
  private java.util.Hashtable
 network.NetworkManger.poolManagers
 [class=java.util.Hashtable]
private java.util.Hashtable
 network.NetworkManger.poolManagers[write:1][write:2]
 [class=network.PoolManager]
  private java.util.Vector
 network.PoolManager.availableTransports [class=java.util.Vector]
private java.util.Vector
 network.PoolManager.availableTransports[write:1]
 [class=[Ljava.lang.Object;]
  private java.util.Vector
 network.PoolManager.availableTransports[write:1][0]
 [class=network.Transport]
private java.lang.Object
 network.Transport.messageProcessingLock [class=java.lang.Object] -
 field that is not serializable

 Is it possible that this object (held by the session) will not be
 serialized
 at all??

 Thanks, Eyal.
 --
 View this message in context:
 http://www.nabble.com/Serialization-problem---detaching-an-oblect-from-session-tp20211477p20211477.html
 Sent from the Wicket - User mailing list archive at Nabble.com.


 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]



 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]




 --
 View this message in context: 
 http://www.nabble.com/Serialization-problem---detaching-an-oblect-from-session-tp20211477p20212873.html
 Sent from the Wicket - User mailing list archive at Nabble.com.


 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Serialization problem - detaching an oblect from session

2008-10-28 Thread eyalbenamram

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 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 J2ee specs?


 igor.vaynberg wrote:

 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 (since most pages in my
 app
 are hoding a pointer to the session) Here is the exception:

 http-6789-6 ERROR lang.Objects - Error serializing object class
 screens.Login [object=[Page class = screens.Login, id = 4, version =
 0]]
 org.apache.wicket.util.io.SerializableChecker$WicketNotSerializableException:
 Unable to serialize class: java.lang.Object
 Field hierarchy is:
  4 [class=screens.Login, path=4]
MySession screens.Login.ns [class=MySession]
  private _community [class=core.community.User]
public core.community.TransactionManager
 core.community.User.transactionManager
 [class=core.community.TransactionManager]
  private core.transportLayer.Protocol
 core.community.TransactionManager.protocol
 [class=core.transportLayer.Protocol]
private network.NetworkManger
 core.transportLayer.Protocol.network [class=network.NetworkManger]
  private java.util.Hashtable
 network.NetworkManger.poolManagers
 [class=java.util.Hashtable]
private java.util.Hashtable
 network.NetworkManger.poolManagers[write:1][write:2]
 [class=network.PoolManager]
  private java.util.Vector
 network.PoolManager.availableTransports [class=java.util.Vector]
private java.util.Vector
 network.PoolManager.availableTransports[write:1]
 [class=[Ljava.lang.Object;]
  private java.util.Vector
 network.PoolManager.availableTransports[write:1][0]
 [class=network.Transport]
private java.lang.Object
 network.Transport.messageProcessingLock [class=java.lang.Object] -
 field that is not serializable

 Is it possible that this object (held by the session) will not be
 serialized
 at all??

 Thanks, Eyal.
 --
 View this message in context:
 http://www.nabble.com/Serialization-problem---detaching-an-oblect-from-session-tp20211477p20211477.html
 Sent from the Wicket - User mailing list archive at Nabble.com.


 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]



 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]




 --
 View this message in context:
 http://www.nabble.com/Serialization-problem---detaching-an-oblect-from-session-tp20211477p20212873.html
 Sent from the Wicket - User mailing list archive at Nabble.com.


 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]


 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 

-- 
View this message in context: 
http://www.nabble.com/Serialization-problem---detaching-an-oblect-from-session-tp20211477p20213300.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Serialization problem - detaching an oblect from session

2008-10-28 Thread Igor Vaynberg
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 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 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 J2ee specs?


 igor.vaynberg wrote:

 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 (since most pages in my
 app
 are hoding a pointer to the session) Here is the exception:

 http-6789-6 ERROR lang.Objects - Error serializing object class
 screens.Login [object=[Page class = screens.Login, id = 4, version =
 0]]
 org.apache.wicket.util.io.SerializableChecker$WicketNotSerializableException:
 Unable to serialize class: java.lang.Object
 Field hierarchy is:
  4 [class=screens.Login, path=4]
MySession screens.Login.ns [class=MySession]
  private _community [class=core.community.User]
public core.community.TransactionManager
 core.community.User.transactionManager
 [class=core.community.TransactionManager]
  private core.transportLayer.Protocol
 core.community.TransactionManager.protocol
 [class=core.transportLayer.Protocol]
private network.NetworkManger
 core.transportLayer.Protocol.network [class=network.NetworkManger]
  private java.util.Hashtable
 network.NetworkManger.poolManagers
 [class=java.util.Hashtable]
private java.util.Hashtable
 network.NetworkManger.poolManagers[write:1][write:2]
 [class=network.PoolManager]
  private java.util.Vector
 network.PoolManager.availableTransports [class=java.util.Vector]
private java.util.Vector
 network.PoolManager.availableTransports[write:1]
 [class=[Ljava.lang.Object;]
  private java.util.Vector
 network.PoolManager.availableTransports[write:1][0]
 [class=network.Transport]
private java.lang.Object
 network.Transport.messageProcessingLock [class=java.lang.Object] -
 field that is not serializable

 Is it possible that this object (held by the session) will not be
 serialized
 at all??

 Thanks, Eyal.
 --
 View this message in context:
 http://www.nabble.com/Serialization-problem---detaching-an-oblect-from-session-tp20211477p20211477.html
 Sent from the Wicket - User mailing list archive at Nabble.com.


 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]



 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]




 --
 View this message in context:
 http://www.nabble.com/Serialization-problem---detaching-an-oblect-from-session-tp20211477p20212873.html
 Sent from the Wicket - User mailing list archive at Nabble.com.


 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]



 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]




 --
 View this message in context: 
 http://www.nabble.com/Serialization-problem---detaching-an-oblect-from-session-tp20211477p20213300.html
 Sent from the Wicket - User mailing list archive at Nabble.com.


 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]