Hi folks

I am in the hell of class loading, and need some serious help. I have the following application layout:

tomcat/shared/lib/
class A (need access to POJO)

webapp1/
POJO java class
hibernate3.1 and the rest of third party jars

webapp2/
class C (need access to A)

My questions are:

(1) do I must put POJO (generated java file by hibernate) in webapp1/ ? because I don't (and put POJO jars into shared loading space, I saw many Error on BasicLazyInitializer, CGLIB Enhancement failed .... combined with NoClassDefFoundEorr: org/hiberante/proxy/HibernateProxy, I couldn't really pinpoint the reason.)

(2) if I put POJO into webapp1, then above errors are gone, but since Class A needs access to POJO and putting Class A into webapp1 is NOT an option for me, that means I have to put POJO into shared loading space as well, which seems very WRONG. And it tomcat logs does report it violates loading constraints.

What are my options then? any help? (btw- this is with tomcat 4.1.x)

Thanks

Oliver

It sounds like what you are doing is returning Hibernate persistent objects to your client, which you should not be doing. From your description, it appears that some object with a persistent collection associated with it was returned. Don't do that. Hibernate replaces the standard java collections with Hibernate implementations, and they will be sucked along with the parent object and sent to the client.

What you need to do is use a Data Transfer Object design pattern. Create classes that serve solely as data containers to ship results back to the client. Do not expose your O-R persistence layer to the client layer.

Thanks for the reply.
I realized that exposing this O/R might be a bad idea.
Any pointers on further guidence on this?

Thanks

Oliver

place hibernate3.jars on the "client" or use a DTO as explained.