|
||||||||
|
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 |
||||||||
Guenther, you are correct. The returned object claims to be an initialized, proxy instance.
So why would it return a non-proxy instance for a find() on a clear()ed EM, but a proxy instance otherwise?
Also, for an initialized proxy, all the internal fields appear to be 'null', and not hold any value.
The issue that exposed this to me was that there's some code doing some javabeans api manipulation on the objects we're getting back from entityManager.find(). It works fine when we get back non-proxied object, but fails miserably when we're dealing with javassist proxies.