I have some classes that have collections in them. I create and populate them which works fine. Then when I save, hibernate replaces the normal ArrayList and HashSet, etc. collections with hibernate internal versions. Is there any way to prevent this replacement? What is the purpose of it if hibernate can already handle persistence of the regular java util collections?

I am serializing my hibernate objects so I want to not have to serialize these hibernate collection classes as well.


Thanks!

Bump. Please excuse my "nevermind." In fact hibernate does replace classes. Anyway to stop this?

This causes me to need to serialize the hibernate collections too. Along with any exceptions they may throw. Its hard on my RMI system. It forces me to control the loading of my classes since remote loading of classes can toss a runtime exception just because the net cable came unglued...

No.
Hibernate will not work, as it needs to distinguish between initialized and not initialized list/sets etc.
See the discussion here
http://forum.hibernate.org/viewtopic.php?t=946665&highlight=serialize

The last approach in this discussion might be useful to you as well.

You may consider to create a dto object properly initialized to exchange data and then extract the information back in Hibernate objects .