Hibernate version: 3.1

We have hibernate sitting behind ejb's and it is looking like the mapping sets are the PersistentSet object, is there a way to get around this and just use the HashSet object so we do not have to include the hibernate.jar file in the client war file. We have the POJO hibernate data objects in our ejb client jar and this is being used in the client war file.

Use the interfaces, that's what they're for. Use Set, not HashSet or PersistentSet. PersistentSet implements Set, so all will be well.

Currently, our domain objects are declared as interfaces

IE..

public class Cat{
private Set kittens = null;

public void setKittens(Set set){ }
public Set getKittens(){ return kittens; }

}

What the problem is, the PersistentSet Implementation is still required on the client side because of serialization across the wire, from our distributed components...

How are other people getting around this??

The only thing we're thinking about doing is having an adapter pattern utility class inside our ejb that introspects the object that is going to be returned to the portal, and convert the hibernate specific impl (PersistentSet) to something like HashSet ?

The other thing that is causing problems (we believe) is that our client portal server is on jdk1.3 and the app server is 1.4.x so we're getting major/minor errors... We believe it's directly related to the hibernate.jar (3.1.x) is it jdk 1.3 compatible ? we've tried distributing the hibernate.jar to the client server to see if that would fix our problem... (even though we shouldn't have to do that) and that's where we're getting the major/minor errors....

Any thoughts, much appreciation.

You shouldn't be returning results that come directly from the persistence layer to your client. Use the Data Transfer Object design pattern. You need to decouple the two layers.