Some more info and other options...
-----Original Message-----
From: Randy Puro [mailto:randypuro@xxx.com]
Sent: Thursday, March 24, 2005 11:45 PM
To: Alon J Salant
Subject: hessian/hibernate stuff
Hey Alon-
I found some good threads regarding your issues. A couple of
interesting points in a nutshell:
1) If you want to use hessian, some have recommended NOT putting the
hibernate.jar on the client. This will effectively perform some of the
scrubbing you want. Supposedly, when hessian deserializes the object,
if it can't find the original collection class, it will revert to using
the default collection equivelant. I guess then that you'd only have to
special handle uninitialized lazily loaded collections; although I'm not
certain they could still be properly handled when returned to the
server.
2) The better option sounds like using Spring's httpinvoker. From what
I understand, it uses normal java serialization methods, of which the
hibernate classes have built in special handling to make everything work
appropriately. Sounds like you'd get deserialized objects on the client
with the same unitialized lazy relationships (which, if accessed, would
properly throw lazyinitializationexceptions.) You still get the http
wire protocol. Only loss would be hessian's ability to service non-java
clients, but it sounds like that's not an issue.
I'm not sure why I wrote all that - better to just show you the threads:
http://forum.hibernate.org/viewtopic.php?t=932461&highlight=hessian
http://forum.springframework.org/viewtopic.php?t=897&highlight=hessian+h
ibernate
Cool - it all sounds like a lot of fun!
rp
Received on Fri 25 Mar 2005 09:50:42 -0800
This archive was generated by hypermail 2.1.8 : Thu Sep 28 2006 - 20:16:41 PDT