I saw that there is many users that talking about avoiding dependency with Hibernate, especially with the Persistent* (Collection Set/List, ...) class/package when POJOs are "probably" used in distributed environment. Data are serialized and sent to a remote computer under the form of Java Object - I suppose so - This my case and I got a ClassNotFoundException because there is a runtime dependency even if our POJOs do nt explicitly use Hibernate in our source code (except via the hbm file...).

Does Hibernate team have some tips to give us, to help us to find a clean solution - From my side :

1) I'm going to bind my client with the hibernate-core. This is the worse case scenario because
memory space constraint, etc...

2) Some people seems having extract Collection package to reduce the size of import library but how can we be
sure that we have all dependencies ?

3) Just send the data in ASCII form such as XML, well...

4) During the serialization, do not serialize the class with org.hibernate.* but what about the reverse operation ? because we
still need to re-attach objects when they return back to the server.

5) Does Hibernate plan to give us a "distributed version" for real distributed objects.... a very-very small dependency ?

Thank you very much for your answer.

Ok, I found an interesting link : http://www.mojavelinux.com/blog/archive ... f_my_pojo/