I have a RMI Client - Server architecture where I am not permitted to share the Hibernate jars on the server with the client. My problem is when I dont want to load collections/associations at all, what do I do to share the persistent beans with the Client?

If I do this:
At server:
Parent P = session.createCriteria(Parent.class).setFetchMode("children",LAZY);
session.close();
return P;

I get a un-marshalling exception at client for Hibernate Sets. The only solution for me seems to be nulling all the un-required associations before returning a persistent bean. But that defeats the purpose of not loading associations when you dont need them.

I would love to have a option with Criteria to set a fetch mode to NONE. So I never fetch a association.

Thanks for your help and attention.

--

Hibernate has it's own collection implementation whether lazy or not. You'll need DTO to match your requirements

Unmarshaling and Marshaling lazy-loading collections over RMI should work just fine as long as hibernate2.jar odmg.jar and cglib.jar are present on the client. I do it all the time, so I am pretty sure it works.

Yes but

Ah, should read more closely :)