I have the following situation:

In a httpSession (I'm using struts) i have a bean which holds a collection of type A, a collection of type B, an instance of a C object. The objects in collection A are already present at the database, and have been previously loaded. This session gets this way when I reach the last step of a process of getting info about a new user. So, when I have all this data in hands, I have to connect them, so all of them can be persisted. The new data is going to be related to those in the collection A, which are already present in the database.
A completely fresh object is going to appear, and is going to be related to all this data.
the question is: is there an especific order to handle this info, call each setter methods (remember: each setter method passes one of these objects as arguments)? Do I save the new bean before or after saving all the rest?
I know the question is not well formed...but, the main is: is there a correct order to call session.save(obj) for each object ?

Thanks

I'm sorry, Ot

thanks a lot for your reply, but i found a way to do it almost completely. the problem now is about the collection which has data loaded in a previous session. i can set all attributes of the other instances (they are all new objects i'm going to insert in the DB). but when touching the data previously loaded, i get this:


The collection is full of "lotes" instances. those instances where retrieved in a previous moment in my application flow. now i need to relate them whit new data i'm creating now, and update those "lotes".
what am I missing?

thanks

Either you session lifetime is loo long, or your design isn't that good (loading an object and try to update a transient version of is)
Have a look at session.evict().