Entity EJB on a client - Best Practices

[octaviob]

I'm working on an EJB client application on Eclipse RCP.
I'm getting a MarshalException when transfering to the client entities with recursive bidirectional relationships (plus several other relationships). This exception seems to be caused by serialization limitations in Hibernate,
but I'm not sure.

After several searches and no clear answer to my problem, I'm arriving to the conclusion that it is best to 'construct' complex objects on the client by getting finer grain entities from the server and performing final assembly on the client.

Likewise, the database should be updated by merging finer grain entities. This puts more EJB logic/code on the client than I originally intended.

Any comments on best practices for using entity EJBs on a client will be greatly appreciated.

thanks,

Octavio

[waynebaylor]

what's the entity code look like? have you tried using eager fetching?