I’ve just fixed an issue in my application which has arisen since the upgrade to v6.3 and I thought I should pass on some details.
Since the upgrade, when I was attempting to save changes to a particular entity in my application I was receiving an exception regarding an unfetched attribute. This had me scratching my head for quite some time, looking at view definitions etc and debugging the object graph at save time in order to see if I could determine why/how the attribute was not being loaded.
However, I have since discovered that it seems to be due to having a fetch type of ‘lazy’ on this attribute. Changing the fetch type to eager seems to have fixed the problem:
@ManyToOne(fetch = FetchType.EAGER) @JoinColumn(name = "NON_CUSTODY_HOLDING_ID") protected NonCustodyHolding nonCustodyHolding;
I wanted to pass this on because I’m not sure if it is a bug or expected behaviour between the version numbers - but it was definitely a breaking issue in my application until I resolved it.