Persistence session

[vaagesh Chnadra]

Hi All,

Does Objects those placed in "Persistence session" must be serilalizable also required to over write hashcode() and equals methods.

[Ankit Garg]

What exactly do you mean by "Persistence session"??

[vaagesh Chnadra]

OK Ankit,

I will elaborate my question in detail

Clarification 1:

Objects placed in HTTP Session must be Serilizable and also should over write equals() and hashcode() methods

Clarification 2:
Objects placed in Hibernate Session must be Serilizable and also should over write equals() and hashcode() methods

[Paul Sturrock]

Which session are we talking about here, an HttpSession or Hibernate's Session? Or both?

[William Brogden]

I know of no reason to create equals and hashcode methods for objects serialized by the HTTP - Servlet API session mechanisms. After all, it is the String name that is used to recover the object reference.

Bill

[Paul Sturrock]

William Brogden wrote:I know of no reason to create equals and hashcode methods for objects serialized by the HTTP - Servlet API session mechanisms. After all, it is the String name that is used to recover the object reference.

Bill

What about clusters?

[William Brogden]

What about clusters?

I dunno, what about clusters, why would a session shared between clustered servers treat the retrieval of a reference differently?

Looking forward to expanding my understanding...

Bill

[Jeanne Boyarsky]

For clusters, you need to implement Serializable to be able to write to and read from disk. I don't see why you would need equals() and hashCode() though.

[Gregg Bolinger]

It is a popular misconception that hashCode provides a unique identifier for an object. It does not. hashCode and equals are used for Object equality comparisons, not serialized retrieval.