|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
I think the unanswered question, is whether org.hibernate.event.spi.LoadEventListener.isAllowNulls() is intended to cover the condition of the entity not being found when attempting to look it up. I'm not sure of what else would of been intended from the LoadEventListener class which has this comment "Defines the contract for handling of load events generated from a session." Allowing nulls or not on the load events, seems to be the purpose. So, the suggested patch is sounding correct to me. in which case the org.hibernate.test.jpa.proxy.JPAProxyTest should be testing for a null being returned from EntityManager.find rather than an EntityNotFoundException being thrown.
Lets get confirmation from others on this (will try on IRC or email soon).