When using hibernate and spring boot the HibernateUnproxyObjectAccessHook does not cover all scenarios

[dwtalk]

The implementation of HibernateUnproxyObjectAccessHook and how it plugs into the GlobalIdFactory's create method covers most scenarios.

However, I did find an scenario where when a Query is build and run byInstance, the instance ID of the hibernate proxy is assumed and not the id of the desired object (which is proxied).

Specifically the error I was seeing is: "ENTITY_INSTANCE_WITH_NULL_ID" which will be resolved with a pull request momentarily.

I was able to correct the issue using the ObjectAccessHook in the createInstanceId method of the GlobalIDFactory just as it is used in the create method.

[dwtalk]

Pull request created for this 1 line fix

#566

[bartoszwalacik]

Thanks, PR merged, will be released tomorrow

[bartoszwalacik]

released in 3.3.5