I have an entity (Table) into wich i add entities column, the Object table. is saved or updated, the problem is in IN ANY CASE I DO NOT CALL the saveOrUpdate method, the save is called in the method FaceletViewHandler.renderView(FacesContext, UIViewRoot) Line: 459 (Spring framework with facelets, hibernate (latest)) and i dont want the object to be saved or updated.

And the save or update method is not the one in my DAO...


how it is possible ?

I'm not sure if the problem is this:

- you want to save an object, but others are (also) getting saved. If so maybe you have specified a cascade type on the owning object that is causing the owned objects to be saved?

OR

- something about the facelet view handler calling save is wrong...but I don't understand.

-larry

I dont want any object to be saved, and in MY code i never call any "Write" method, but during the render view cycle, the object is saved in the database, and i dont want this. I don't have any event listener, or method in the facelet who can potentially call a save procedure, actually the whole code look like a "Hello World"

You could try posting your code and mappings here (don't forget to use the [code][/code] tags to make them readable).

Also, you could try setting breakpoints in the save/update/saveUpdate methods of org.hibernate.impl.SessionImpl, and see where in the stack a call comes from.

-larry

A few possibilities -- depending on your flush settings, any query could cause the session to flush the dirty objects before the query is executed

I'm not familiar with Facelets, but if there is something like OpenSessionInView or OpenEntityManagerInView operating, I've seen some versions that have an explicit flush in their clean-up code.