Hello all,

I am working on a project that includes GWT and Hibernate.

If I am not wrong, Hibernate doesn't leave our beans mere a POJO. It just completely changes our beans if we see it by refactoring, most probably when the bean is not completely loaded, it becomes instance of some MyBean$$EnhancerByCGLIB class. So when we try to send this bean to GWT client, that bean is no more IsSerializable. So as a temporary solution, I have prepared one convertor using refactor that converts my Hibernate bean to simple IsSerializable kind of POJO. But as project is growing, issues are rising and I need to enhance the convertor for copying object graph.

So I want to know that if anyone has faced the same issue earlier and is there any stable solutions for this issue. I came across one technology called "Hibernate4GWT". I didn't get time to try it out. But its documentation says that it supports GWT 1.4 and 1.5 version. so again want to know that what if I am using GWT 1.6.

Looking for solution as soon as possible..

Thanks in advance

Hi Vishal,

We have used hibernate and GWT in the project and we faced the exact same problem. We had annotated hibernate mappings in our Hibernate POJO's and couldn't use them at the GWT client side at all. So we had equivalent set of client side POJO's and used BeanConverter of spring framework to convert GWT Server side POJO's to GWT Client side POJO's

I would like you to suggest you below options

1. The whole idea of separating GWT Server side with GWT Client side is at the server side you compute whatever data model you need but pass only the required data to the GWT Client (since most of them are Async RPC Ajax calls), So try to pass the data to the GWT client side layer via JSON, XML etc other formats which makes data loading faster. If you pass the server side POJO's as is, GWT client side will convert them to equivalent data notations in javascript causing performance overhead

2. Based on our experience in the project, its better to have different set of POJO's for GWT Client and Server layer, coz you may need additional data to be displayed at the client side for which its not good to always modify your domain objects (which is one-to-one mapping with your db)

3. Try DWR (http://directwebremoting.org/)

We do this in Terracotta's reference application Examinator: http://www.terracotta.org/web/display/o ... ementation

We made a specialized library called "Pojoizer" to strip the Hibernate stuff from POJOs returned from Hibernate. My recollection on the subject is that there are 1 or 2 blogs that demonstrate the technique, and one or two libraries that do as well.