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
On Mon, Mar 28, 2016 at 1:22 PM Lovro Pandzic
wrote:
> I am confused how you are "mind mapping" PreparedStatement parameters and
>> entity construction into the same conversation. We are not instantiating
>> entities based on PreparedStatement parameters
>>
>
> I'm not sure I understand you
>
> I am confused how you are "mind mapping" PreparedStatement parameters and
> entity construction into the same conversation. We are not instantiating
> entities based on PreparedStatement parameters
>
I'm not sure I understand you, I haven't mentioned PreparedStatement
parameters anywhere
JPA says that portable applications (portable across JPA providers) should
have default constructor. Every provider supports things beyond the
spec. Heck JPA also says that getters and setters need to be public, but
we don't enforce that either.
On Mon, Mar 28, 2016 at 7:27 AM Vlad Mihalcea
wr
Nowadays the entity instantiation and data population is done like that:
final Object object;
if ( optionalObjectKey != null && key.equals( optionalObjectKey ) ) {
//its the given optional object
object = optionalObject;
}
else {
// instantiate a new instance
object = session.insta
Commented on the Jira.
I am confused how you are "mind mapping" PreparedStatement parameters and
entity construction into the same conversation. We are not instantiating
entities based on PreparedStatement parameters
On Fri, Mar 18, 2016 at 2:32 AM Lovro Pandzic
wrote:
> Hello,
>
> I'd lik
