It's always polite to indicate which version of jboss you are using, even if you have just posted 10 other messages where you do say. Someone (me) might not have seen the others or might not remember what they said.
In jboss 3, and possibly 2.2.x, this problem can occur if you have not properly implemented equals and/or hashcode on your pk object.
Something very odd is going on if updates are deleting and recreating entities. Perhaps if you have this pk problem the container can't tell they are supposed to be the same entity.
Appologies on not reporting my version, I am working with the a build from this morning, with exception of the proxy.compiler package which has given me all kinds of other problems. That is from prior to the 3/7 update. I will investigate your recommendations. Thanks! :)
David, you are so money! Right on the mark with that advice. I identified one primary key problem right away and corrected it. But the other...that was a doosey. I misspelled one of the words in the class name and decided to rename it. But both my compiler and I missed three occurrences of the original spelling in the source code, all the in .equals method. All because of a change to a single character! :( Doh!
Corrected that and the delete and insert issue went away. Thanks,