Hi,
I agree that Optional should not be used for entity attributes.
Nevertheless, they can still use it for getters if they use field-based
access:
http://stackoverflow.com/questions/24975813/hibernate-orm-supporting-java-1-8-optional-for-persistence
As for the Session-level API, we could add th
No the concern is the 2 cases where we are asked to create and return an
entity given only an id. This happens in 2 cases:
* In response to Session#load / EntityManager#getReference
* When building a non-eager "to-one" association reference, which is really
a specialization of the first case
On
Thanks.
After a quick look, one of key points is
Loader#doQueryAndInitializeNonLazyCollections?
This is the point where the entities get loaded and properties set during
the load from database?
On Thu, May 5, 2016 at 9:46 PM, Steve Ebersole wrote:
> Look at usages of Instantiator interface
>
>
>
Look at usages of Instantiator interface
On Thu, May 5, 2016, 2:08 PM Lovro Pandzic wrote:
> Sorry for late reply.
>
>
> Well you mentioned Java 8 parameters names in the subject. I have no idea
>> what "Java 8 parameter names" might mean outside of the support added in
>> Java 8 for named para
Sorry for late reply.
Well you mentioned Java 8 parameters names in the subject. I have no idea
> what "Java 8 parameter names" might mean outside of the support added in
> Java 8 for named parameter binding. So if that's not what you mean, what
> do you mean?
>
> Based on some of your other rep
