Hi, I am having an issue with a commit that should not happen. I have a one to many association between A and B. When I create an instance of A it somehow gets placed in the current session. I tried removing any association to A from B's collection of A and removing B from A. When I flush and commit, A somehow gets committed. How can this be? Any help would be greatly appreciated.

I think that you're saying that B contains a collection of As? Is that right? If you're creating an item in a collection owned by a persitent object, then that item will be written to the DB unless you have the inverse="true" attribute on the collection.