On Wed, Aug 19, 2009 at 8:01 PM, C N Davies <c...@cndavies.com> wrote:
> will get the exact error you reported. The error never made any sense to me > because I can't understand how the entity could be detached, because there > was no entity (for the City). > It doesn't quite sound like my case, but causes me to think more about mine. The error states the entity is "unmanaged" but you describe it as being "detached". Looking at 8.2 "Entity Lifecycle Management", there is no use of the word "unmanaged". I'm trying to figure out what JPA considers "unmanaged". Using the diagram at the bottom, it appears New/Transient, Removed, and Detached states may all be "Unmanaged" since they aren't, well, "Managed". The child entity was not Removed or New, at least not as a result of my actions. I'm pretty sure it was Detached, but since that happens "all the time" I don't see how that could be the problem. What is "Transient"? Could my object fall into this state once in a while? Can anyone tell me exactly what an "Unmanaged" instance is? -- Daryl Stultz _____________________________________ 6 Degrees Software and Consulting, Inc. http://www.6degrees.com mailto:da...@6degrees.com
