While researching Second Class Object behaviors, I found this in the specification 6.3:
Second Class Objects of mutable system classes and persistence-capable classes track changes made to them, and notify their owning FCO that they have changed. Since converted classes most resemble persistence-capable classes, I proposed this change to 6.3: Second Class Objects of mutable system classes, converted classes, and persistence-capable classes track changes made to them, and notify their owning FCO that they have changed. But this implies that we enhance converted classes. So: 1. What does JPA do about converted classes? Does it enhance them so they track changes made to mutable instances? 2. What are the requirements for converted classes in JDO? Just follow whatever JPA does? If we really want to require enhancing converted classes, we should be specific about it. And add a test case or three to the TCK. To test this, we will need a mutable converted class, perhaps by adding a mutator method for the x value. Then, modify the x value and see if the instance is marked as dirty. Craig L Russell c...@apache.org
