I am developing a web application using hibernate and wondered if using a uniquely generated id like a session variable and then assigning that as my key id would be an issue? That way I could add and delete child elements to a parent before I saved the parent, right??? I want to be able to do:

Parent p = new Parent();
Child c = new Child();
p.setChildren(new HashSet());
p.getChildren().add(c);
c.setParent(p);

without having to issue a session.saveorupdate() first before i can add another child item to the parent. Also knowing the key id of the child item will also allow to delete the item if i wish to. Am I way off the mark here???


regards


Andrew

I too am looking for a discussion on this topic.

I think I realize why we want to let hibernate manage the identifiers. But, their availability prior to save() in a webapp is quite useful.

I look forward to discussion of strategies in this area.



Joe