Hi,

we have a fat (Swing-)Client that connects to a JBoss that runs ejb3-persistent beans. As all Collections we send to the client (finderResults, but also mapped relations) are Hibernate-Collections, we have to distribute the Hibernate-Classes to the Client - is there a way around that, eg. is it possible to have a fetch.type=eager and have plain java-collections for mappings instead of Hibernate-Collections?!

The brute-force approach would be to have some DTO's and move all contents from the original objects into the DTO's (and back again on update), but I would be very happy, if we could just hand out the persistent classes to the client&get them back again on update...

Thx for any help
stefan

http://forum.hibernate.org/viewtopic.php?t=932779

i use a util class that takes hibernate collections and converts them to java collections... i'm not sure there are many other options if you don't want to include the hibernate jar on the client.

I 'd have the same use case.
I can imagine that depending on what my code does with those collections, their implementation does matter.

For example: in a certain list I am doing a lot of inserts, so a LinkedList implementation would perform a lot better then an ArrayList. Then again, in another list I am doing a lot of index gets, so I 'd prefer ArrayList.