We have a very complex legacy relational data model, that does not map directly into objects. We also have God objects very weak cohesion.

The intension is to break these God Objects up. But we may be left with a situation where we have a object which will need to be persisted to multiple tables, some of these tables will map to business objects.

We will have rows that match to objects but we will need to extract that information into a object.

I guess hibernate uses joins, but would appreciate a link to this subject. How Hibernate copes with what could be complex multiple joins, or are views a better option.

Although we will look at refactoring the God Classes we may not be able to refator too much, time constraints.

Thanks for any links.

Hi,

no idea what you mean with God classes and I don't think this really belongs to this forum. If it all you should try the main Hibernate User forum. Have you read the Hibernate online documentation? And if you really want to dig into Hibernate get a copy of Java Persistence with Hibernate.

--Hardy