I am not sure about the removing and inserting part but cascade=none doesn't mean that. For that you need to set the inverse=true so that hibernate does not bother with this side of relation. For the strange behaviour, please explain more what happens in your code.
A little different sceanrio but it's kind of related.
I have a bidirectional mapping
Mapping file TCrmConfigEvents.hbm.xml has this association defined
Mapping file TCrmFixClientConfig.hbm.xml has this association defined
<!-- corresponding bidirection assosiation of above one-->
<column name="FixClientConfigId" />
<column name="CrmLinkId" />
Mapping file TCrmFixClient.hbm.xml has this association defined
Mapping file TCrmClient.hbm.xml has this association defined
<column name="ClientId" />
Now I'm saving the TCrmConfigEvent as below..
TCrmConfigEvent event = new TCrmConfigEvent();
event.setTcrmFixClientConfig(fcc); //fcc is an instance of TCrmFixClientConfig passed to this method
At this point hibernate generates the insert sql to insert a row in the corresponding table of TCrmConfigEvent, which is fine. But it also generates the 10 update sql to update TCrmFixClient object. TCrmClient has set of 10 TCrmFixClient objects. So hibernate seem to be reaching the object in the following path. TCrmConfigEvent-->TCrmFixClientConfig-->TCrmFixClient-->TCrmClient-->set of 10 TCrmFixClient.
My question is when I save TCrmConfigEvent why hibernate reach to TCrmFixClientConfig even though inverse=true on that association as show above? I'm trying to optimize the number of queries it generates. I just want to save the TCrmConfigEvent with a reference to TCrmFixClientConfig but don't want to save TCrmFixClientConfig or any associated object from there on.
I know it's bit detailed information but hopefully it convey the scenario as is.