Hi, I'm using Spring + Hibernate with annotations in an application based arround a root object with several collections which in turn have several collections. I was wondering how wrong it would be to call save and update methods only on the root object whenever i need a change to be persisted.
For example:
My root object is called Petition and it has a collection of Task elements wich has a collection of Assignment objects. Should i add assignments to a taks, would there be much of a difference if instead specifically saving the changes to that task i called a method which persists changes in the entire Petition object?

Hi,

always persisting your root object is possible. Especially if you for example always access your Assignments and Tasks by first retrieving an Petition. There might be a little overhead involved when always persisting root object compared to a single task. Depending on your application that might be of importance or not.
The right approach really depends heavily on your overall requirements and architecture.

--Hardy