Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipselink-users] NullPointerException in sequence of persistent property mutations

On Fri, Sep 6, 2013 at 6:28 AM, Tom Ware <tom.ware@xxxxxxxxxx> wrote:
I am not sure what the intention of the spec is, however, as noted in the bug we do have to merge the association itself (but not the object).

Would this be true even if the relevant join column were marked insertable=false/updatable=false?

To fully understand, I assume the reason you have to merge the association itself is so that if--after persisting the root object--I set something new "into" that relationship, the entity manager is aware of the change.  Is that right?  If this is so clear, why is it that no other JPA provider does this?  Not pointing fingers, just trying to understand.

Best,
Laird

--
http://about.me/lairdnelson

Back to the top